MSAccess.exe has generated errors

[fernin8r]

HELP... Somethin' crazy is goin' on

Alright...

I've tried asking IT. I've tried searching google. I've got to go right to the source.

I have an Access97 db that is stored on a network for ~12 users to work with. This db has been up and running with no problems for about 4 months.

A problem occured over the weekend, when a user tried to update a new record. It wouldn't work. This problem was only on a certain table/form. All other tables/forms worked fine. Assuming there was just some user error, we figured closing the db would fix it.

Then on monday, after presummably fixing the problem, it got serious. The database wouldn't open. First, it started saying "MSAccess.exe has generated errors..." and then it would close right away. So I started using the backup. The backup worked for a little while then it too wouldn't open. Instead of the first error though, this one said "Unable to open Form 'Summary' ... name misspelled..." yet the name was correctly spelled AND nothing happened that would've changed it. With this error however, I could hold the shift key and view the db that way, but our main form was not working. So I re-issued the backup again. It worked for a little while too and then started getting the first error "MSAccess.exe has generated errors..."

So, my co-developer and I decided to stay late that night and rush the release of a newer version that we had been working on, thinking that something internal was corrupt and we couldn't see an easy fix.

The new version has one main form with 16 subforms. all accessing 2 tables using SQL statements for their RecordSource.

After hours of work...the next day with a new version and the same errors. Every time we would open it..."MSAccess.exe has generated errors..." then it would close right away. Even when I tried holding the shift key down so that just the db window would open, it won't work. Which tells me it's not our code.

WHAT IS THE DEAL? Any help on this will be greatly appreciated.

Thanks

 

[neileg]

Mmm...

I don't think I have any brilliant ideas, but try these. I appologise if you've already done this.

I presume that your new version is based on the same data? How have you transfered the data? If your new version is a new FE, could the data be corrupt in the BE, thus preserving the problem?

Have you tried the compact and repair? There are more thorough repair utilities available to fix corrupt data from the MS support site.

Have you tried a new database and import all the data and objects?

Have you tried drinking beer? If you drink enough, you'll stop worring about the database.

 

[Parker]

"Unable to open Form 'Summary' ... name misspelled..." yet the name was correctly spelled AND nothing happened that would've changed it. With this error however, I could hold the shift key and view the db that way,

Hate to over simplify and state what may be the obvious but have you tried removing this item and any reference to it?

Also what OS?

If it is FE-BE is the data stored on a machine with a different OS than the FE?

As well as checking the integrity of the data have you checked the integrity of the OS?

Failing all else forget the beer try a good bottle of sprits, dance about the office in an obviously drunken stupor and claim no fault of yours due to diminished responsibility. (You may get fired but it's not your prob anymore)

 

[fernin8r]

Bottom's Up

Due to the responses I received. I think the bottle sounds very tempting.

I have tried repairing and compacting. I've tried using back up versions. I've tried using a different DB.

Just a little more information though.

We are using MS Win2000 will a Novell Server (I know, I know, I've heard this was a bad combo. Like water and oil)

Another one down....
Today we had another DB go down that has nothing to do with the original DB. I think we may have a network issue.

All the DBs seemed to be doing okay too, until that one weekend. Another question... MS Access seems to be reading the file path with ~ instead of the complete path.

Example:

C:/Local/ME-Estimator/Database/me.mdb

becomes

C:/Local/ME-Estim~r/Da~ase/me.mdb

Has anyone every seen this? Is this normal? The reason I ask is because we started getting Runtime Error 3433 which won't allow the .Update command to run. It states that the format of " C:/Local/ME-Estim~r/Da~ase/me.mdb " is not an mdb format? WHAT???

Thanks for your input...

 

[Parker]

Example:

Yes I have seen something similar before, but not on a Novell system and not with Access files it was with another db.


Had a ssimilar instance on a Samba server under SuSe Linux 7 a couple of years ago. Something happened to the naming conventions and the whole server got screwed. We later found out that we had caught a virus from somewhere.

We managed to recover from backups in the end after cleaning down the server and re installing. Can't remember the name of the virus off hand but we are much more careful these days.

So you may find that it's a prob on the server.

I don't like W2000. Having said that, I don't much like windows full stop. But needs must (unfortunately)

I looked at windows 2000 and decided that it was just an exceptionally poor attempt by MS to emulate a reasonable OS----- in my books it fails, miserably.

I really can't imagine W2000 being a good mix with any non MS OS although I can understand some peoples liking for it.