Replies

Charlotte:
Thanks for the clearest “DAO/ADO” explanation I’ve yet seen. I’m also trying to deal with the issue. Have been trying to implement one of Helen’s ‘Archon’ code bits dealing with adding to combo box underlying tables ‘on the fly’ without success and suspect this issue may be affecting it since I’m working with 2k ‘out of the box’.
Since I’m also subject to “denseness”, I have a dumb question: When the references are changed, does the change apply to Access 2k in general, or just to the database open at the time?
Again … thanks for your help and willingness to share your insights and experience.

Thanks, Mark
Up to this point there haven’t been any problems with cbo response speed.
Acutally, I was sitting here engrossed in the app on Sunday and suffered a momentary ‘brain f__t’.
The main slowdown occurs with entry and edit forms based on complex queries drawing from many tables.
In general, is there an performance advantage to basing forms on such queries, or is it better practice to base forms on the tables underlying the queries?
I’m one of those poor souls who is just beginning to get into vba since I’ve been too busy building an app that mostly works to spend the time learning vba.
Obviously, if I had it to do over, etc, etc, …

Mark (et al):
Thanks for the quick advice. Will probably abandon the idea, since these are all “small” tables. Have already discovered the ‘referential integrity’ factor, but things still worked.
All tables have primary keys (autonumber); sql statements for cbo’s have “ORDER BY” statements.
You’re right in that the ‘larger’ tables are the ones that change and would remain in the server back end.
Logistics problem is met by placing a new SE zip front end file on the server, and having regional IT guys download it from WAN to LAN (even the users can get it from their individual office LANs).
Having said all this, thanks again, and consider the idea abandoned.

Yes … the user wants to show the address AND worksheet data in the cell, although I can’t think why!

It seems to me that showing the Row/Cell headings should be sufficient.

Thanks for the answer … we’ll look into it!

Your problem MAY lie in the ‘Users’ group permissions, which is a default group from which individual users can’t be removed. I remove all permissions from the Users group.
Once the default Users group have no rights to anything, create a new group(s) that have the appropriate rights and assign users to these groups as appropriate.

As the previous responder stated, it is also necessary to remove Admin from the Admins group.