In previous databases, I have done it all in Access; the backend and the frontend.
Recently, I have begun transferring (more out of interest at first, but now with the plan to replace the originals) it all to a VB5 frontend that accesses the backend MDB.
I am avoiding Data Controls, and am using recordsets, SQL statements, etc. to load records. These I load into variable arrays, and going from record to record (using Next, Previous buttons, etc) shows the contents of the appropriate one in the appropriate Text Box etc. When saving, it changes the contents of the corresponding variables, opens a recordset, puts those variable values into it and updates it (so it updates in the backend MDB).
Is this an acceptable method? Are there any dangers, concerns I may be missing? It works okay here at home; on a standalone PC. But how would it run on a network with up to 15 clients accessing it?
Also, any relationships I put in using code; I haven't set up any in the MDB. I find I prefer doing this. But then again, I may be missing something.
Recently, I have begun transferring (more out of interest at first, but now with the plan to replace the originals) it all to a VB5 frontend that accesses the backend MDB.
I am avoiding Data Controls, and am using recordsets, SQL statements, etc. to load records. These I load into variable arrays, and going from record to record (using Next, Previous buttons, etc) shows the contents of the appropriate one in the appropriate Text Box etc. When saving, it changes the contents of the corresponding variables, opens a recordset, puts those variable values into it and updates it (so it updates in the backend MDB).
Is this an acceptable method? Are there any dangers, concerns I may be missing? It works okay here at home; on a standalone PC. But how would it run on a network with up to 15 clients accessing it?
Also, any relationships I put in using code; I haven't set up any in the MDB. I find I prefer doing this. But then again, I may be missing something.