VBA Project - Error Message

[bharlow]

Every few weeks one of our DB's give the following error message...

The database can not be opened because the VBA project contained in it can not be read. The database can be opened only I fthe VBA project is first deleted.

Deleting the VBA project removes all code from modules, forms, and reports. You should back up your database before attempting to open the database and delete the VBA project.

We are having to pull in a clean back up copy each time.

Does anyone know what might be causing this problem and have some ideas how to avoid?

 

[HiTechCoach]

What version of Access including Service Packs?

Is you database split? It should be. It is a must if shared!

Is the front end local on the PC and NOT on a network share?

Is the front end an MDE/ACCDE? I would recommend this to keep the VBA form getting corrupted.

 

[bharlow]

Hello HiTech Coach

The Access version is 2007

The DB is split with a front end [User Input] and back end [Reporting]

The front end users access the DB via terminal services

The front end is ACCDE.

I hope that helps narrow the issue.

Thanks for any advice!!

 

[HiTechCoach]

Which update of 2007?

 

[bharlow]

I do not know what you mean by "Which Update of 2007"

 

[HiTechCoach]

Have you installed the SP2 update for Office 2007?

On the terminal server, does each user have their own copy of the front end?

 

[bharlow]

Apparently not. They are loading it now.

Could that have been causing the problem??

 

[HiTechCoach]

If the users on the terminal server as sharing a front end, this definitely can cause corruption.

 

[bharlow]

The Network guy is loading SP2 so hopefully that will fix the problem.

I was wondering if it had anything to do with the Front End shared users being open while running the macros on the Backend. I was not sure if the linked tables were causing the problem. I have been getting a lot of You do have exclusive access messages and I thought the front end users not shutting down properly might be the problem.

Thanks for all you help!!

 

[DCrake]

It's a bit pointless have one front end that everybody logs into even if the data is linked back to a back end. It's just like having multiple sessions open on one machine with many users using it simultainiously. Every user should have their own copy of the front end on their pc then they are opening their Jet database. This is the most likely origin of the error you are encountering.

David

 

[bharlow]

David,

If each user has their own copy of the front end DB on their machine and I have 15 users, does that mean I need to link in all 15 tables to the backend and Union the tables or is there a better way that I am missing?

Thanks for your thoughts on the subject!

 

[DCrake]

The back end on the shared server would only contain the tables. The front end would contain evertything except tables. You would use the Link Table Manager to link the user interface (Front End) to the data in the back end.

As long as each user has read/write persmission and access to the shared location they will all have access to the live data.

There are many topics on FE/BE on this forum.

This gives you the flexibility of being able to made modifications / updates to the front end independantly then distribute it to all users.

David

 

[bharlow]

Thanks David

I'll look into how to accomplish this.