M
Morgan
I have a small Db that is split, back side on a server,
front side for clients. I am having a lagging problem
with the db. When I made the Db I also had to make a vb
app to run as a system service, and it access a table on
the back side on the server. The vb app monitors certain
fields for number changes. I have determined that the vb
app is not slowing down the Db. This is were I think the
problem is: I really needed the vb app to access a Query.
But since the db is split, there are no queries on the
back side, so what I did was made a table called [EMS
Tbl] and I made one query to append to the table, and one
query to delete from the table. So what happened is when
a user click an "OK" button the two queries will run,
First it will delete all the records to the table, and
then second it will append all the updated data to the
table, something like refreshing the table. Is there a
way to simplify that process, or maybe is there a way to
use code to single out just the record that is being
worked on.
DoCmd.OpenQuery "Delete EMS Query" (and code here to just
specify that one record)
I don't know. This is the only way I can access the
information I needed to be monitored from an separate vb
app. But I need the app, so does anybody know of an
simpler way of doing what I said above, or maybe I need
to look elsewhere for the lagging problem.
Thanks, Morgan
front side for clients. I am having a lagging problem
with the db. When I made the Db I also had to make a vb
app to run as a system service, and it access a table on
the back side on the server. The vb app monitors certain
fields for number changes. I have determined that the vb
app is not slowing down the Db. This is were I think the
problem is: I really needed the vb app to access a Query.
But since the db is split, there are no queries on the
back side, so what I did was made a table called [EMS
Tbl] and I made one query to append to the table, and one
query to delete from the table. So what happened is when
a user click an "OK" button the two queries will run,
First it will delete all the records to the table, and
then second it will append all the updated data to the
table, something like refreshing the table. Is there a
way to simplify that process, or maybe is there a way to
use code to single out just the record that is being
worked on.
DoCmd.OpenQuery "Delete EMS Query" (and code here to just
specify that one record)
I don't know. This is the only way I can access the
information I needed to be monitored from an separate vb
app. But I need the app, so does anybody know of an
simpler way of doing what I said above, or maybe I need
to look elsewhere for the lagging problem.
Thanks, Morgan