Editing Objects Without Nav Pane

[JeffGeorge]

Is it possible to access database objects without using the nav pane? I'd like to keep the nav pane turned off on a shared database so that the regular users don't get confused, but I have need to edit various objects. I could just turn it on and off as needed but I was hoping there was another way to access the objects.

[John_G]

Hi -

If you are using a shared database with anything other than tables in it, stop and rethink your setup. Having a shared (network) database with all the forms, queries etc. in it is asking for trouble. Generally speaking, it is not if, but when, you will encounter some form of corruption.

For multi-user applications, you should be using a split database, where only the data (tables) are stored in a network files (the back-end), and each user has their own copy of the file with all the report, queries, etc (the front-end). By doing this, you can make changes, and test them as required, and once everything is working, distribute updated versions of the front-end to your users. No users should be opening the back-end directly.

As for the navigation pane, you can keep it visible in your working, development copy of the front-end, and then turn it off in the version you distribute to your users.

HTH

John

[JeffGeorge]

I understand the inherent dangers faced with this database but, unfortunately, the person that originally designed it did it this way and it would be way too much work to redo it, especially since it's being phased out. I just wanted to know if there was some way to edit the objects without using the nav pane while the database is still active.

[June7]

VBA code can open an object in design view. Tables and queries can be edited without opening by using TableDefs and QueryDefs collections. I have code using those collections to create tables and to edit query but haven't used in a long time. It was a tool created in early stages of db development.

I also have code that opens a report in design view, does some edits, saves report, then prints report. Why do I do this? - it's a long story. Normally, building code to edit objects is way more effort than just manually opening and doing the edit.

Edits to a shared db file cannot be saved unless the db is opened exclusively.

Splitting a database is not that difficult.