Any Ideas?

[Taliesyn]

I have an Access 2003 database running on a server. Today (for about the 5th time in 6 months) Access reported that the VBA was corrupted and tried to repair the database. As usual, it didn't work but I don't know what to do to prevent this in the future. Any ideas? Our IT bloke is scratching his head cos he doesn't know either .......... and (remembering the "talk to a programmer" thread) No, I haven't got a clue what is going on!

 

[Insane_ai]

Try to decomplie then recompile the VBA.

Here's how: http://support.microsoft.com/kb/819780

An update to VBA may also be in order. Get it here: http://www.microsoft.com/downloads/...BA-CD3D-458B-9729-AB9094C9BD3F&displaylang=en

 

[boblarson]

When you say - "I have an Access 2003 database running on a server." What do you MEAN you have it running on a server? Is this a split database (frontend/backend where the backend has only tables and the frontend is a copy on each user's machine)? If not, it NEEDS to be to avoid corruption problems.

See here for more info about that.

 

[pbaldy]

Is the application split (copy of front end on each user's PC, back end on the server)? If not, that is likely the cause of the corruption.

 

[gemma-the-husky]

I actually put code in to my front end, to check the folder in which the drive is located. (mapped drives). if the drive letter is (arbitrarily) greater then "L" say - it won'y run.

Just to try and prevent the newtowrk dbs being launched inadvertently