RTE 2147024770 (Access97)

Topic

New Reply

I have a machine that is running windows XP with Office 2002 EXCEPT Access is version 97. a DB which opens fine on a machine running windows/95 and Access97, generates a runtime error upon opening a report. The error is as follows: runtime error -2147024770(8007007e) Method. ‘CurrentDb’ of object ‘_Application’

the code on this report is as follows:

Private Sub Detail_Format(Cancel As Integer, FormatCount As Integer)
Dim db As DAO.Database
Dim rst As Recordset
Dim strSQL As String
Dim strSpeciality As String

Set db = CurrentDb

the code stops right there and generates the error. There seem to be no missing libraries but after some research, i cannot locate any data about this runtime error. Any assistance is appreciated.

Reply | Quote

Replies

I would first suspect a Missing Reference. What is background on machine in question? That is, does it work with other Access databases? Was anything recently changed/upgraded?

Reply | Quote

I presume you probably already checked this based on the fact you declared db as DAO.Database, but do you have a reference set to DAO? And if so, by chance is the DAO version 3.6? That could cause this kind of problem. In general it’s pretty dicey trying to run a two version old app with current versions of the other office apps as DLLs and whatnot get replaced. I’ve never seen that error message, but I suspect there are hundreds that I’ve never seen, so . . .

Reply | Quote

Thank you for the replies Mark and Wendell – I have checked the references and the user’s machine has DAO 3.51 which is the same reference checked on my machine. I did change the machine from 3.51 to 3.6 as suggested, but to no avail. The error msg generated is the same. Recent changes are as follows: this machine came loaded with Office XP and Windows XP. the office package didn’t include Access at all (any version). our company uses office 97 so we attempted to install office97 from the original Office97 CD but learned that it isn’t that simple. Office XP had to be removed before office97 could be installed. office 97 was loaded onto the machine (which included access). officeXP was also reloaded so both versions of office can be used. Service Packs 1 and 2 were also loaded. the only obstacle in the process was the need to change a font name (hatten.ttf) which caused launch problems. at that point access worked. (for about 3months) Then, last week, the wizards, input masks, etc stopped working in access so the user could not easily create db objects and the error msg in question began also. the machine has been taken down and reloaded with office 97 and xp. this has not resolved the error msg. Another incidental is that we use MSMail for our interoffice mail which WindowsXP does not support. outlook 97 doesn’t work with windowsXP and outlookXP doesn’t support MSMail. Therefore we have Outlook 2000 running as a stand alone program. Now if you can weed through that and have an idea for an avenue to venture down, i’d sure appreciate it.

Reply | Quote

I hate to be the bearer of bad tidings, but I think you may have to format the hard drive and start over and just use Office 97. Not a happy thought, but with the various constraints you have, trying to run parts of 3 versions of office is a recipe for trouble. And unfortunately, removing Office XP doesn’t really get rid of all of it. If you could use Outlook XP, you could just run Office XP as Access 2002 can open and work with an Access 97 DB, but you can’t make any design changes. Unfortunately you can’t use Outlook 2002, so . . . .

Let’s see if anyone else has a better idea, but unless they do I would recommend starting over from scratch.

Reply | Quote