ruudschiphorst
New member
- Local time
- Today, 19:48
- Joined
- Feb 10, 2009
- Messages
- 2
Hello people,
Since I'm new at these forums, I suppose I'll introduce myself first. My name is Ruud, I'm Dutch and I've been developping in MS Access for a reasonable period now. I work in a small business with 3 co-workers.
I hope this is the right forum, if not; my sincere apologies.
As for my question, we've recently finished a database for a client of ours, who in turn sold it to 2 of his customers as a pilot for a bigger audience. The expectation is, that in about a year, our project will be used in about 20 companies.
As the product grows, we will want to change our basic table structure and relations between them, including the changing, adding and deleting of field names and relations for the sake of a more flexible database and other insights we missed or didn't have before.
At this point, we conluded that if we use the replica option of Access and provide an empty Master, the entire database at our client's customers will be flushed, as our master will be 'last edited'.
Our other option would be to write a quite extended procedure to make a copy of the current records (client side) to an empty database, overwrite their current backend with our new and improved one, then go right back to importing the old records from the new, temporary database. The problem with that, other than it will take a lot of time, would be we'd have to adjust our our script every time in case we rename FIELD_1 to FIELD_2 to exactly match to eachother. Also, this is very delicate and subject to import faults from our side due to spelling errors and such.
Short version: we only want to copy the table structure and relations, without editing or, heaven forbid, deleting the records at our clients.
Is there a method we're missing or overlooking?
Any insights are also very welcome.
Thank you in advance
Since I'm new at these forums, I suppose I'll introduce myself first. My name is Ruud, I'm Dutch and I've been developping in MS Access for a reasonable period now. I work in a small business with 3 co-workers.
I hope this is the right forum, if not; my sincere apologies.
As for my question, we've recently finished a database for a client of ours, who in turn sold it to 2 of his customers as a pilot for a bigger audience. The expectation is, that in about a year, our project will be used in about 20 companies.
As the product grows, we will want to change our basic table structure and relations between them, including the changing, adding and deleting of field names and relations for the sake of a more flexible database and other insights we missed or didn't have before.
At this point, we conluded that if we use the replica option of Access and provide an empty Master, the entire database at our client's customers will be flushed, as our master will be 'last edited'.
Our other option would be to write a quite extended procedure to make a copy of the current records (client side) to an empty database, overwrite their current backend with our new and improved one, then go right back to importing the old records from the new, temporary database. The problem with that, other than it will take a lot of time, would be we'd have to adjust our our script every time in case we rename FIELD_1 to FIELD_2 to exactly match to eachother. Also, this is very delicate and subject to import faults from our side due to spelling errors and such.
Short version: we only want to copy the table structure and relations, without editing or, heaven forbid, deleting the records at our clients.
Is there a method we're missing or overlooking?
Any insights are also very welcome.
Thank you in advance