ADO RecordSource loses Recordset data after a few minutes.

  • Hi

    I'm using an Access 2003 adp, which has worked really well for many years. However, we have recently changed to Windows 7. We have also installed Microsoft Office 2007 without Access then loading 2003. I haven't found any horror stories on the Web about this; however, I have a few. I wonder if anybody could help me with a couple of them:

    1. A subform recordsource, derived from an ADO recordset, has suddenly started to crash the subform. It says the recordsource (and cites the SQL which produces the recordset) doesn't exist. All the subform entries show '#NAME'. It is fine for a few minutes - all data present - then the above happens. Has something changed which causes the data to be lost???

    2. When printing some reports, the error message comes up that the database must close: 'Microsoft Office Access has stopped working - a problem caused the program to stop working properly. Windows will close the program and notify you if a solution is available'. The reports have been working fine for a long time...

    I will be updating to a Visual Studio solution, but it is such a big database that it will take a considerable period to complete.

    Any help will be gratefully recieved

    Thanks

    Paul

  • Any luck with solving this, PaulSp? It would be useful to know since my organization will be upgrading to Win7 soon and I'm supporting an Access2003 to SQL app.

    ______________________________________________________________________________
    How I want a drink, alcoholic of course, after the heavy lectures involving quantum mechanics.

  • Hi ToddASD

    No. All very frustrating. I can't find any logic in what is happening...

    I wish you all the best in your own upgrade.

    Paul

  • Hi...

    I have worked with Access 2003 apd projects for many years, and have also used the projects on Win 7 without problems. I normally use a runtime version of Access on the client though. But what I have seen over the years, is that the Access project itself gets corrupted sometimes, and opening a certain dialog or report makes Access crash. The ony way to fix it is to find an older version and either do your changes over again or it sometimes helps to just copy the dialog or report from one adp file to another.

    Trond

  • Hi Grasshopper

    I've been trying exactly what you say. This has always worked well in the past. However, I haven't got it cracked yet... I'll keep trying.

    Many thanks for your comments.

    Paul

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply