G
Guest
I'm curious as to whether there is a way to easily replace forms etc. without
affecting any table data using some kind of automated proces (run by VBA,
most likely).
Basically what I have is a couple different people using an mdb file with
forms and such that I developed, but all with different data, no central
server. etc. I'm almost continuously making additions and bug fixes to forms,
codes and reports, and I'd like a fast easy way to distribute these to all
the users and allow them to update the forms on their own. The easiest way I
can think to do this hypothetically is to simply redistribute a copy of the
blank dB I use for building, and somehow combine them at the user end
(obviously the end user would have to initiate. That's not a problem.). The
only way I can see to do this is to export all the table data and then
re-import it into the new mdb file, but I have two issue with this:
1) Can I use VBA from one database to access the others, especially if
they'll be getting renamed in the process? (ie, dB.mdb --> dbBack.mdb,
dbUpdate.mdb --> dB.mdb - will the VBA continue to run if its own file gets
renamed in the process?)
2) I'd rather not have to touch the data at all due to the possibility of
corruption in the transfer process (granted I'd have the backup still). Is
there a way to Import Forms instead of Importing Data?
Better yet, is there a way to compare two mdb files and export the changes
into a VBA process that might create the changes in the other mdB files when
run?
(By the way, I have used VB.Net 2005 in the past, just not for database
controls, so could I potentially use this to transfer forms? I thought about
using it for the forms to begin with, but as I said, I've never used it in
conjunction with databases, so I wasn't comfortable trying to make it work
reliably, as I've seen that there are problems and complications.)
I'm sorry if this seems like a stupid question, I just can't keep taking
time to document every change I make to code and forms and individually place
them in each active database.
Chris
affecting any table data using some kind of automated proces (run by VBA,
most likely).
Basically what I have is a couple different people using an mdb file with
forms and such that I developed, but all with different data, no central
server. etc. I'm almost continuously making additions and bug fixes to forms,
codes and reports, and I'd like a fast easy way to distribute these to all
the users and allow them to update the forms on their own. The easiest way I
can think to do this hypothetically is to simply redistribute a copy of the
blank dB I use for building, and somehow combine them at the user end
(obviously the end user would have to initiate. That's not a problem.). The
only way I can see to do this is to export all the table data and then
re-import it into the new mdb file, but I have two issue with this:
1) Can I use VBA from one database to access the others, especially if
they'll be getting renamed in the process? (ie, dB.mdb --> dbBack.mdb,
dbUpdate.mdb --> dB.mdb - will the VBA continue to run if its own file gets
renamed in the process?)
2) I'd rather not have to touch the data at all due to the possibility of
corruption in the transfer process (granted I'd have the backup still). Is
there a way to Import Forms instead of Importing Data?
Better yet, is there a way to compare two mdb files and export the changes
into a VBA process that might create the changes in the other mdB files when
run?
(By the way, I have used VB.Net 2005 in the past, just not for database
controls, so could I potentially use this to transfer forms? I thought about
using it for the forms to begin with, but as I said, I've never used it in
conjunction with databases, so I wasn't comfortable trying to make it work
reliably, as I've seen that there are problems and complications.)
I'm sorry if this seems like a stupid question, I just can't keep taking
time to document every change I make to code and forms and individually place
them in each active database.
Chris