Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DB Update and Copy Problem 1

Status
Not open for further replies.

georgesOne

Technical User
Jul 2, 2004
176
JP
Good morning,

I am working on a DB which will have FE/BE and also replication for laptop users (and for faster data transfer).
The work is still in progress, but I have some urgent requests to release certain parts.

My two questions:
Is it possible to
a. keep my personal DB as .mdb (in order to make further changes) with master design authority for general DB changes
and b. to provide the users with .mde FE (so that they can not acces the code) and at the same time update these with new tables, forms etc. from my DB during the replication process?

2. Is there any possibility to create a log when either the master BE, the replica BE or the FE at the user side has been copied or is there any possibility to make copying not possible or useless?
Would e.g. encryption of a large DB slow transfer processes
significantly?

Thanks, georgesOne
 
Good Evening George.


First point : NO

Once it is an MDE then thats it.
But its easy to issue users with new versions.

Idea:
In the BE add a table ( I call mind tblSetUp ) with a PrimeKey SetUpId of type Yes/No, default Value Yes. ( This guarantees table will only ever have one record in it. )
Add field Version of type Single

Then store a version number in there in the main BE

Add some code in the startup form that checks tblSetup!Version. If the FrontEnd is an earlier version ( higher integerpart ) then present message to user and shut down.
If version is incremental ( higner fraction part ) present warning to user but let them continue.

That way YOU control who can use your BE with what FE and you make the users come to you to get new FEs.


The BE can then grow and develop at its own pace.
Synchronising replicas with the designMaster will incorporate all new table design changes as you go.


Item 2
If you COPY a Design Master it just becomes a Replica.
Other than that you desire is in the relms of Windoz operation, active directory and all that Jazz - it ain't Access.



'ope-that-'elps.



G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.
 
LittleSmudge,

thanks, I think it 'elped.
I will try out your idea (it's getting more and more) and let you know later...
Anyway, other comments are still welcome.

Thanks, georgesOne
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top