.accde file
I just upgraded my 2003 database to Access 2010. I was using a .mde file on a Novell-Delivered Application window for users to access the database. I updated to .accde and pushed that out.
Now I am having extreme issues. People can get in, but then it freezes. They try to go back in and get 'The database cannot be opened because the VBA project contained in it cannot be read. The database can be opened only if the VBA project is first deleted. Deleting the VBA project removes all code from the modules, forms and reports. You should back up your database before attempting to open the database and delete the VBA project....." Or that the file is unstable.
I can copy over the original .accde file to the share point and it's works for awhile but once again after you get a few users in it, it locks up and does this again.
I can put the .accde on the user's desktops and it works fine but our IT department is not really liking that as an option, they want it to work from the Novell-delivered Application window.
Any ideas as to why this is failing where the .mde file was fine?
Help would be appreciated.
Thanks
Deanna
Now I am having extreme issues. People can get in, but then it freezes. They try to go back in and get 'The database cannot be opened because the VBA project contained in it cannot be read. The database can be opened only if the VBA project is first deleted. Deleting the VBA project removes all code from the modules, forms and reports. You should back up your database before attempting to open the database and delete the VBA project....." Or that the file is unstable.
I can copy over the original .accde file to the share point and it's works for awhile but once again after you get a few users in it, it locks up and does this again.
I can put the .accde on the user's desktops and it works fine but our IT department is not really liking that as an option, they want it to work from the Novell-delivered Application window.
Any ideas as to why this is failing where the .mde file was fine?
Help would be appreciated.
Thanks
Deanna
ASKER
No, it is just an an application delivered windown. one .accde file for about 40 users........
So that won't work? They have to have it on their workstation?
So that won't work? They have to have it on their workstation?
They have to have it on their workstation?That would be the Best Practices solution.
The key part to properly sharing an Access application is that each user must have there own copy of the front end.
For best performance you want the front end on the local hard drive with linked tables to the shared back end (tables). It is possible to have each user's copy of the front end on a network share as long as each user has their own copy.
My gut instinct tells me that the Nov ell-delivered Application window is not compatible with Access 2010. That could explain the constant database corruption
Boyd Trimmell, Microsoft Access MVP
aka HiTechCoach
ASKER
OK. So our IT guy backed into the 2003 version and found that the .mde file was getting copied locally. He create a command to copy the new one but now we are geting something really wierd.
This is the command:
copy \\fr01apthr001\HRData\HRIS
This is what happens when the .accde opens:
Microsoft Access has detected that this database is in an inconsistent state, and will attempt to revcover the database. During this process, a backup copy of the database will be made and all recovered objects will be placed in a new database. Access will then open the new database. The names of objects that were not successfully recovered will be logged in the "Recovery Errors"table.
It then opens and create a backup on the C drive where it was supposed to be overwriting the existing one.
What the heck and how to fix??? When you open the .accde that was copied to the C drive it works fine......
This is the command:
copy \\fr01apthr001\HRData\HRIS
This is what happens when the .accde opens:
Microsoft Access has detected that this database is in an inconsistent state, and will attempt to revcover the database. During this process, a backup copy of the database will be made and all recovered objects will be placed in a new database. Access will then open the new database. The names of objects that were not successfully recovered will be logged in the "Recovery Errors"table.
It then opens and create a backup on the C drive where it was supposed to be overwriting the existing one.
What the heck and how to fix??? When you open the .accde that was copied to the C drive it works fine......
That is strange.
It may be a permissions issue on the local folder and/or file. The user must have read AND write permissions for the folder. with the .accde.
Have you checked the folder permissions?
It may be a permissions issue on the local folder and/or file. The user must have read AND write permissions for the folder. with the .accde.
Have you checked the folder permissions?
ASKER
I doubt it because it creates the backup on the local drive. AND it is overwriting the existing.
So you click the icon the access database comes up throwing that error and then clicking OK creates a backup.accde file. Or backup(2).accde.... So it has read/write access. I've checked the timestamp and it is updating it.
So you click the icon the access database comes up throwing that error and then clicking OK creates a backup.accde file. Or backup(2).accde.... So it has read/write access. I've checked the timestamp and it is updating it.
ASKER
We took the copy out and the icon on the NAL is working pointed at the C drive. So it has to have something to do with the copy and then open?
How are you opening the database after the copy?
ASKER
We have an icon on the Novell Delivered Application window. You click it, it copied the .accde file to the local workstation, then opens it in Access.
Still no love. At this point IT just has it open the .accde file in Access 2010. The copy part has been taken out.
Still no love. At this point IT just has it open the .accde file in Access 2010. The copy part has been taken out.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you, I'll see what our IT department says.
Access 2003 is more forgiving for haring an mde but there were still issues.
Access 2007 and later do not like to share a front end .accde which o helps eliminate issues. Each user will need their own copy of the front end .accde. No way around it with Access 2007 or later.
In your case, to keep the IT people happy, I place an app launcher .accde on the server. The launcher will copy the front end to the local workstation and then launch it.
Are you creating a trusted location for the .accde on each workstation?
Boyd Trimmell, Microsoft Access MVP