Updating an unlinked table in front end database

  • Thread starter Thread starter cookdw60
  • Start date Start date
C

cookdw60

I am looking for a way to update data in a table from the back end to
front end without linking the table in to avoid the users in front end
from locking and causing problems in the back end. I originally did
this by using make table queries, but I have run into problems with
the table in the front end being referenced at the time by reports
which lock that table. Is there any way to avoid the table from being
locked when being accessed from a query or a report? If not, is there
a better way to update the table to avoid linking and at the same time
table lock issues??
 
Not sure I follow the question.

When you update a table in a multi-user environment, there is always a
chance of conflict. Someone else may be trying to update the same thing at
the same time. That's why there has to be a locking strategy. Otherwise
people would be corrupting the data, or overwriting each others' changes. A
multi-user database without a locking strategy would be a disaster.

Given that, your question seems to be how to make changes to the database
without any locking strategy? I'm not sure I understand that.
 
If you are not going to have a link, then couldn't you set a macro to run a
push (make table) at a certain time when end users won't be updating
 
The Front end database is just being used for reporting. There will
be no updating of records going on there. My question is if I can
update the data in the Front end that is ONLY being viewed through
reporting, and no actual updating is done EXCEPT for when an update
process is run from the back end... does that make more sense? Back
End stores data, refreshes front end a few times a day with updated
data... Front End allows reporting for the floor to view open accounts
and updated statistics but no updating of records is done in the front
end.
 
The Front end database is just being used for reporting. There will
be no updating of records going on there. My question is if I can
update the data in the Front end that is ONLY being viewed through
reporting, and no actual updating is done EXCEPT for when an update
process is run from the back end... does that make more sense? Back
End stores data, refreshes front end a few times a day with updated
data... Front End allows reporting for the floor to view open accounts
and updated statistics but no updating of records is done in the front
end.
Click to expand...

I don't understand. If you make links to the back end then the front end
will always see the current data. There would be no need to run periodic
updates.

If that is not what you want you could create links in the file you are
calling the back end to the local (non-linked) tables in what you are
calling the front end. In this case the terms are essentially backwards.

A process in the file (that you call the back end) could delete all data in
the linked tables (tables which actually reside in the file used for
reporting) and then repopulate them with the data from its local tables.
The reporting database would then be updated to agree with the "real" data
in the other file.
 
Could you have one version of the front end where you can input data (forms
are set to Allow Additions and Edits whilst other users get forms etc that
don't)?
I've little experience with multiuser environments but I'm surprised to see
a table in the front end. I thought that the idea was to set Permissions for
stuff like allowing editing and inputting. Just when I thought I was getting
the idea!
Evi
 
Back
Top