Database Crashing - Missing VBA Modules

[rage300]

All,

Could really use some help. I have an access database that is used by 4-5 users on a shared drive. It is loaded with VBA and for some reason it continues to get corrupted. The VBA all of a sudden disappears. It was 2003 Access version and is sometimes used by people who have 2007. Could that be the reason? Any thoughts on where I should investigate?

Thanks in advance,

Jason

 

[boblarson]

The database should be SPLIT (frontend/backend with the backend on the server and a COPY of the frontend on EACH user's machine). Nobody should be opening a shared file on the server. Doing so, is a guarantee of corruption. It isn't a matter of IF it will corrupt but WHEN.

So, read this and you'll need to move to a split db and a fe on each user's machine.

 

[Joe4]

The VBA all of a sudden disappears. It was 2003 Access version and is sometimes used by people who have 2007.

Absolutely! This was the biggest source of corruption in our office - users on different versions of Access being in the same database at the same time. That was when we started to split our databases, like Bob recommends. Lo and behold, we have not had any corruption problems since we did that.

 

[rage300]

Many thanks for the quick responses. The challenge I have is that this is part of a replicated DB and this is happening at one of the replicas. Any idea if that will present a problem?

Jason

 

[boblarson]

Many thanks for the quick responses. The challenge I have is that this is part of a replicated DB and this is happening at one of the replicas. Any idea if that will present a problem?

Jason

Does this "replica" have forms, reports, macros or modules in it? If so, you have an even bigger problem. Replication should ONLY be used on tables and maybe queries, but NOTHING ELSE.

You might need the resources here.