S
Steve K
So I have a strange scenario... I have a complex/large database broken into
a FE and BE (multiple actually). If I open the db with the Shift bypass
key... everything development wise (designing of queries, forms, reports,
etc.) works like normal. However, if I open the db and allow the main form
vba code to execute (which includes an append query from a network BE table)
and then switch to the db container and edit queries/forms/reports or create
a new one... Access will auto save any changes made (when editing) or force
me to save (when creating new). I don't get the "Do you want to save your
changes?" question. But again... I do get it if the auto exec vba code
doesn't execute. I believe I've narrowed it down to the append query. If
all the vba code except that query runs... everything works (for developing
purposes) like normal. The moment that query (or any append query for that
matter) runs... then Access starts acting weird by not confirming
changes/saves or it requires me to save (when it's new) before it will
close.
Why would it do this? And how can I get it to act normally even if the
query(ies) run?
Thanks,
Steve
a FE and BE (multiple actually). If I open the db with the Shift bypass
key... everything development wise (designing of queries, forms, reports,
etc.) works like normal. However, if I open the db and allow the main form
vba code to execute (which includes an append query from a network BE table)
and then switch to the db container and edit queries/forms/reports or create
a new one... Access will auto save any changes made (when editing) or force
me to save (when creating new). I don't get the "Do you want to save your
changes?" question. But again... I do get it if the auto exec vba code
doesn't execute. I believe I've narrowed it down to the append query. If
all the vba code except that query runs... everything works (for developing
purposes) like normal. The moment that query (or any append query for that
matter) runs... then Access starts acting weird by not confirming
changes/saves or it requires me to save (when it's new) before it will
close.
Why would it do this? And how can I get it to act normally even if the
query(ies) run?
Thanks,
Steve