exporting a form

[Guest]

I have a DB in production mode and a copy in development. I have made
changes to a form and wish to export these changes from development into
production, however every time I do the old form re-appears in production. I
have deleted the form, compacted and repaired the db and nothing works. Any
ideas please help.

DDBeards

 

[Bill]

If your production "copy" is a "mde" file, and you have a
production "mdb" counter-part which recieves the updated
form, then all you need to do is re-generate the production
"mde" from the production level "mdb".

If your production environment is "split", then you'll have
both "mdb" and "mde" production files present. That might
account for what you're experiencing if you're unknowingly
updating the "back-end" data file.

Bill

 

[Guest]

Sorry, but both files are MDB?

If your production "copy" is a "mde" file, and you have a
production "mdb" counter-part which recieves the updated
form, then all you need to do is re-generate the production
"mde" from the production level "mdb".

If your production environment is "split", then you'll have
both "mdb" and "mde" production files present. That might
account for what you're experiencing if you're unknowingly
updating the "back-end" data file.

Bill

 

[Bill]

You're using the term "export". If you instead "import" from
the development mdb into the production mdb and confirm
replacement, do you get the same result?

Bill

 

[Bill]

You of course have to confirm save when you've finished.

 

[John Vinson]

I have a DB in production mode and a copy in development. I have made
changes to a form and wish to export these changes from development into
production, however every time I do the old form re-appears in production. I
have deleted the form, compacted and repaired the db and nothing works. Any
ideas please help.

DDBeards

You should - I'd almost say MUST - use the database splitter wizard to
create a "backend" (shared, containing the tables) and "frontend"
(with linked tables, containing everything else, and distributed).
This database should NOT be shared.

When you come up with a new frontend feature, you can then simply
overwrite the user's frontend .mdb file (or, better, .mde) with a new
copy; no data will be damaged since it's all safely in a separate
backend database.

John W. Vinson[MVP]

 

[Bill]

I strongly urge you to heed John's advise. It wouldn't even
occur to me to have any other configuration than an mde
front-end with a "data only" mdb backend. That way, as
John alluded to, you simply release new levels of the mde
file whenever a new level is ready for production.
Bill