Design Changes In Shared 2002(XP) Databases

[CWestII]

Does Anyone know how to override the feature in AccessXP that prevents design changes in "Shared" databases while more than one user is in the system?

 

[BuGlen]

Design changes are locked out for a reason. You would not want errors to be thrown at users when a change has taken place during the time they had the project open.

You best options is to split the database into front and back ends. All of the interface elements and queries would be in the front end installed on each workstation. All of the actual data would be in the back end.

Hope this helps.

- Glen

Know thy data.

 

[MichaelRed]

There have been several (to NUMEROUS) discussions re this topis in these fora. Use "Advanced Search" with [Update | FE |BE | MSysObjects] and follow the trail with additional likely keywords found in the threads rreturned.






MichaelRed
m.red@att.net

Searching for employment in all the wrong places

 

[CWestII]

I understand the locking for that reason. The database is split into a front and back end application. However, the reason I need to be able to get around this feature, is that I have developed an "Ad Hoc Report Generator" which uses code to build a report based on selections made by the users. Since the code is creating a report, adding controls, grouping, sorting, filtering and saving, the database looks at this as a design change. This code does not affect the other users in the database because they cannot access that report that is temporarily stored in the database.

 

[MichaelRed]

Your set up is incorrect. If the FE is on each individual DeskTop there is no reason for Multiuser capability (or indication) on that part.





MichaelRed
m.red@att.net

Searching for employment in all the wrong places

 

[CWestII]

In this particular case, I did not set the frontend up to be pushed to each PC. Therefore, the frontend is shared as well. I guess the answer would be to set it up so that it's pushed to each PC.
The only problem I have with that is that when I set it up to run on individual PCs I like to convert them to ".mde" files. However, in this case the Ad Hoc report feature will not work in the ".mde" format either. (which was why I chose not set it up to run that way)

 

[MichaelRed]

Then seperate the "Ad-Hoc" report builder and set it up as a seperate FE (using 2 of them on the desktops). the "Net Cops" will appreciate the effort on your part, as Ms. A. is somewhat of a (network) resource hog even when configured 'properly' and becomes more 'piggish' when the FE is run from the server.




MichaelRed
m.red@att.net

Searching for employment in all the wrong places