Temporary Table vs Update

[m stroup]

I have a form/subform that writes to two linked tables. I don't want data
entered to go to the table until the form is completed and the Enter button
is clicked.

I currently have the data writing to two temporary tables. When Enter is
clicked, a macro runs appending the data to the two permanent tables and then
deletes the information in the temporary tables. It works fine, but I just
read about update batch. Is this a better approach?

 

[Tony Toews [MVP]]

I have a form/subform that writes to two linked tables. I don't want data
entered to go to the table until the form is completed and the Enter button
is clicked.

I currently have the data writing to two temporary tables. When Enter is
clicked, a macro runs appending the data to the two permanent tables and then
deletes the information in the temporary tables. It works fine, but I just
read about update batch. Is this a better approach?

Update batch? I'm not sure what you mean in this context.

Your current approach is what I would do anyhow.

Where do you store your temporary table? In the BE? If so then how
do you keep different users data separate? In the FE? then your FE
is subject to bloating.

See the TempTables.MDB page at my website which illustrates how to use
a temporary MDB in your app.
http://www.granite.ab.ca/access/temptables.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[m stroup]

Thanks for your reply, Tony.

Currently, the database is not split. I am a professional beginner at
access it seems. I am not sure I can split it in the current environment as
I do not have administrator rights to the server, etc.

So, it will probably sit on the server. The form I have created will only
be used by one individual and the reports will be used by several.

I read in a help file that you could place the data on the form to a buffer
so that tables will update on clicking update instead of autofilling.

Would it be better to have my controls (text, combo, etc) unbound, and then
write the data to the table in an event procedure on click?

I am having fun, by the way.

 

[John W. Vinson]

Thanks for your reply, Tony.

Currently, the database is not split. I am a professional beginner at
access it seems. I am not sure I can split it in the current environment as
I do not have administrator rights to the server, etc.

It is JUST exactly as easy to put a split database backend on the server as it
is to put a unitary shared database on the server - and much much safer. See
Tony's website for details.

So, it will probably sit on the server. The form I have created will only
be used by one individual and the reports will be used by several.

If it's going to be used by multiple users - for *anything* - then it should
be split.

I read in a help file that you could place the data on the form to a buffer
so that tables will update on clicking update instead of autofilling.
Cite?

Would it be better to have my controls (text, combo, etc) unbound, and then
write the data to the table in an event procedure on click?

If you don't mind doing ten times the work for very marginal benefit.

John W. Vinson [MVP]