Running Office 97 on win2k.. problem??

kormaster

Senior member
Apr 19, 2001
368
0
0
I am running Office 97 on win2k pro.. WHY??? becuase the database program that my client made for me was made under Access 97 back in the days. He said he has not tried on Office 2000 nor has installed on Win2k. He has only worked on it on win98 or 95.

I mean this guy is OUTDATED but the prog that he made for MS Access is awesome.

Problem is that i keep getting this message why using 97 MS ACCESS

"MSACCESS.EXE has generated errors and will be closed by WIndows. You will need to restart the program.
AN error log is being created. "

WHY WHY WHY?? If the guy made the database for 97 access.. can i use it under Office 2k? Any conflict??

Basically this prog for Access lets me do inventory management and sales info.. like a database. COuld it be the fact that he made it under 97Access and giving me conflict with win2k? WOuld upgrading to Office 2k fix it?? HElp me please.. i am so frustrated at work!
 

tagraff

Junior Member
Jun 18, 2001
9
0
0
Upgrading to Office 2000 probably will not solve your problem, and it could possibly make it even worse. Quite a few people that I have talked to that upgraded/converted databases from Access 97 to Access 2000 have experienced problems during the conversion.

As far as Win2k is concerned, I ran Access 97 on Win2k for a while and never experienced the problems that you are having. If you wait long enough (usually 5-10 seconds) after the error occurs you should be able to press an OK button that will cause a better description of the error to be recorded in the event viewer. That may give you some clue as to what is really causing the problem.
 

kormaster

Senior member
Apr 19, 2001
368
0
0
darn... you think that the database program and table is ONLY for access 97? maybe that is why access97 and win2k is not getting along... damn damn damn... MS people.. think before u make something!
 

Kinesis

Senior member
May 5, 2001
475
0
76
kornmaster you are worrying for nothing. There is more than meets the eye there. I have done development in both Access 97 and Access 2000. Installed Access (or Office 2000) may fix the problem, but like tagraff said not likely. It is not an incompatibility issue. How do I know? I run Access 2000 on my main system and at school. Access 97 on my other system and at work. All are on Windows 2000 OS.

I would ask what patches have been applied (if any) to that version of access. I am sure they may help, but it sounds like a corrupt EXE file. Is the file system NTFS or FAT?

 

kormaster

Senior member
Apr 19, 2001
368
0
0
the file is fat32...... it some of the tables open up fine.. but if i try to access some other tables or database.. sudddenly the message comes out and quits the prog... u think i have messed ACCESS.EXE file?? should i go Office 2k or Office 97??

See this is happening to BOTH of the computer.. i think it's the Office 97 files... i will try to obtain different office 97 cd or go win2k...


hey Kinesis, u said u have done a lot of access development.. i was wondering.. whatever this guy did to access 97 to make it into a nice database system.. (he made butons so that i can access SALES, INVENTORY, BANKING and it opens up little tables so that i can fill out the things.. ) making it work on office2k is not problem?? i really think it is the access97 prog error.. nothing wrong with his design of the database... and no other of his customer who is running the same program under Access97 isnt having this problem.. only in my office.. cuz no one is running win2k.. plus the office 97 i got was from HongKong.. get the picture now.. "FROM HONG KONG" but all other office progs work... this is my first time using access...

And this guy put a protection on his prog so when i bring the files home.. i cant test it under office2k.. cuz i dont have the "admin power" to do so... and this guy is on a business trip until monday.. sigh... what do u think?
 

Kinesis

Senior member
May 5, 2001
475
0
76
OK there is one thing I want to ask is have you repaired the database? If the answer is no then do so. Tools Menu > Database Utilities > Compact Database/Repair Database. Try that, it may correct some part of the problem.

Could be the version, but it is highly unlikely. It would be no problem for office 200 to read the file. Why not try that. Copy the database file and then open it in a Office 2000 Access. The thing with Office 2000 to is, it can detect errors and repair some if its own files. Never know. But Office 97 is very unlikely the problem.

But hey I have been wrong before..