Database Programming - Loading Correctly?

[Valleriani]

Using VB

Okay, I have a Access database going on that stores all the data. Would it be better to do either:

1) Get the info from the database, store them in variables(arrays), call them when needed, then when needed have them save all using some sort of /save command or such.

OR

2) Call the info when needed right from the DB, and directly save it when something changes..



This is using the Microsoft DAO 3.6 Library...
What I'm asking is. Can I call straight from the DB all the time? Or will it cause lag... Basicly: Should it be called and stored into variables then saved back into the DB using those variables, so it would not save if a crash occured? Or can I call it right to the client, and have it save soon as something updates?

This is for server to client stuff.

--

Basicly the first one would be /save only when I type it, or per few minutes.

And the second one would be real-time. Saving when something changes.

Got to remember there may be 100-150 people using it always.

[Valleriani]

Basicly, Would be better to call tons of words and such stored in the ACCESS DB, put them into variables, then when done save back with a save command?

Or call them right up without storing, and save it whenever something changes.

[szlamany]

Our technique is to load as little data into the VB side as possible - so sharing is not effected.

Then as soon as possible after the user changes a value we write it back to the database.

[Valleriani]

Thank you for the quick responce. I'll try that