Cpuser...no problems...easy....well...after a few months
No problems, the normal database actions Save/Update/Delete/Search are fairly straight forward. Your next question would seem to imply createing a new .mdb, providing preset Field definitions, and populating with data from an existing .mdb. Once again yeap not a problem, a bit more complex but still readily achievable
Post actual questions, and include the names of your controls, to get usable code snippets back. What l mean by that is start your app at the beginning, and then ask questions as problems arise.
Hope this gives you hope, just reply with questions
Not too sure what you are hoping to do
Do you mean that each time the program is run, it will create an entirely new blank mdb file. Then allow the end user to process their own records. How would a user therefore go back to an already created database for further processing. Could think in terms of an additional user id field and use SQL to restrict access to only those records which have the user's id.
On another note don't even think about data binding controls, this is a really dump approach which will cause you heartache and grief later in your project. Think in terms of data classes and a three tier approach. Yes people will say this is over-kill but what the hell it is the most logical approach.
VB can quite happily create new mdbs with data definitions etc, though l must admit to being a bit rusty on this. Will drag out an old project tonight and refresh myself on it. Takes a bit of effort but is worth it.
Ahh GrassHooper the smoke clears
Ok will search out an odd app which did this and extract details for you...not a problem...ya want a demo project, (vb5 sp3) email me at [email protected]