M
m stroup
I have just recently split my database. I have both the front end and back
end on a shard drive and have copied the front end to the applicable
machines. The data entry form on the front end writes to two temporary
tables. The data is appended to two permanent tables upon the
btnUpdate_click action.
Is it reasonable to have temporary tables set up for each front end. That
way user A can close the application without updating and the information is
there when he reopens is. It also would prevent data entry competition
within the temporary table.
What would be the best way to change this? I could copy the table structure
but I am unclear about the linking.
Any suggestion/help would be appreciated
end on a shard drive and have copied the front end to the applicable
machines. The data entry form on the front end writes to two temporary
tables. The data is appended to two permanent tables upon the
btnUpdate_click action.
Is it reasonable to have temporary tables set up for each front end. That
way user A can close the application without updating and the information is
there when he reopens is. It also would prevent data entry competition
within the temporary table.
What would be the best way to change this? I could copy the table structure
but I am unclear about the linking.
Any suggestion/help would be appreciated