Well, in the famous words of Miss Emily Litella, "never mind".
I figured out my problem, and it was a result of revisiting very old code and forgetting what I intended when I wrote it.
Sorry for the meaningless noise.
I have a front-end database that links tables from a couple of back-end databases (all MSACCESS/DAO). As part of a schema upgrade I executed the following:
Dim dbLog As Database
Set dbLog = ws.OpenDatabase(CurrentProject.path & "\" & "Log.accdb")
...
dbLog.execute "create table...
I use unbound fields in a form header in a continuous form to allow users to enter filter criteria. This work well.
However, this form doesn't allow changes to data (it's for users to select a row, which then opens in a dialog form), I want to set Allow Edits=False. When I do this, the...
I have a split database with a single back-end accessed from two identical copies of a front-end. The back-end and front-ends are all located on a 1Gbps LAN. In this configuration, performance is abysmal because all query execution happens on the front-end systems, and involves shipping all...
Thanks for all the excellent info. The automatic front-end update might be doable. There will be issues when a combined BE/FE upgrade is pushed, and some clients still have a running FE instance that's no longer compatible with the new BE table structure... I guess checking the "required...
I understand that's one canonical solution, but it isn't optimal when pushing out FE updates.
I want to understand the actual source of the problem to determine if the no-tables solution will work.
I have to update a split Access DB from single-user to multiple
users. All persistent data is in the BE, FE contains the app plus a
few tables that would be TEMPORARY if Access supported the concept.
The client has access only to the runtime, not the development
environment.
I see three...