G
Guest
I am a newbie at Access programming. I just finished an application that
works perfectly as a standalone .mdb file but now I would like to split the
database into a back end and a front end.
I used the database splitter wizard in Access 2003. It worked well, but now
when I run the front end some things don't work quite as they should.
The first issue I encountered appears to be related to 'requery' commands on
my forms: in certain cases, when the underlying data is changed I issue a
requery command to update the data shown in the form. In the mdb application
the form is updated perfectly, but in the fornt end it is not. If I close the
form/application and reopen it, the updated data is shown correctly. Thus, it
would appear that the 'problem' relates to how quickly the back-end tables
are updated. Is there a way to force the back end tables to update, so that
when I issue my requery command the form will indeed show updated data?
works perfectly as a standalone .mdb file but now I would like to split the
database into a back end and a front end.
I used the database splitter wizard in Access 2003. It worked well, but now
when I run the front end some things don't work quite as they should.
The first issue I encountered appears to be related to 'requery' commands on
my forms: in certain cases, when the underlying data is changed I issue a
requery command to update the data shown in the form. In the mdb application
the form is updated perfectly, but in the fornt end it is not. If I close the
form/application and reopen it, the updated data is shown correctly. Thus, it
would appear that the 'problem' relates to how quickly the back-end tables
are updated. Is there a way to force the back end tables to update, so that
when I issue my requery command the form will indeed show updated data?