Export of Access Structure Only 2

[CactysJack]

I have searched the forum for info on my question but notice similar inquiries get no replies. My problem is I would like to export new structure changes to a remote user accessible only by floppy disks. And of course retaining their data changes.

It seems the $700 MS Office XP Developer has maybe such a routine (Indirect Synchronization) but that seems like overkill for one function.

Any ideas?

TIA,

John

 

[danvlas]

In SQL, you should play around with:
Create Table
Alter Table
Drop Table
Create Index

and so on.

In DAO, you can use the TableDef object and the Fields collection:

tdf.Fields.Append (FieldObject)
tdf.Fields.Delete "FieldName"

Good luck.



Daniel Vlas
Systems Consultant
danvlas@yahoo.com

 

[CactysJack]

Dear Danvlas,

I'm sure if I were more experienced I would be able to understand your sugggestions but unfortunately I am too green.

SQL is still foreign to me and I haven't a clue what DAO means. That gives you an idea of how green I am. Basically I am working myself through Access and apparently haven't gotten very far yet. Even so I do have an nice project more or less completed by guessing, reading my $75 worth of manuals and occasionally asking on this forum and dumb luck.

But I'll work on it and thank you for the assistance.

Best,

John

 

[Lightning]

The simple, long-term solution to this problem is:
ALWAYS split your applications into a Front-end interface and Back-end data-file.
By planning for this right from the start of your development, it becomes a simple matter to update the application by providing a new Front-end to your users which will link to the back-end data-file at any time, without disrupting the back-end data-files in any way. Check the on-line Help file topics for
Database Splitter
Linked Table Manager
for detailed info on splitting databases.

The solution to your immediate problem depends on how accessible your user is. If they are close to where you are, create a split version of your app, take it to them and install the Front-end interface. Then use the FILE > GET EXTERNAL DATA > LINK command from the menu to connect to the existing data tables in your older version. You could then delete all Forms, Queries, reports, etc from the old version, making it the Back-end file.

HTH
Lightning

 

[CactysJack]

Lightning,

Thanks for the great advice. I haven't studied splitting yet but it's in my book (tutorial) and it looks manageable. Very good advice.

I'll get on it right away.

Yes, the application runs only a few minutes away and is just in beta now.

John

 

[CactysJack]

I split the database as suggested. I then seemed to run into trouble trying to delete tables etc. from replica at remote location.

But I finally realized you can synchronize not just over LANs etc but with any file on your system (DUH). So I put the remote (replica) on a ZIP, brought it back, put it in my drive and followed instructions to synchronize.

"Open the DB to be synchronized with.
Select Tools/Replication/Synchronize Now
And follow my nose."

I then will take the ZIP back and reinstall the (split)DB at the remote.

Thanks all for the guidance.