Split Database

[ddrew]

I wonder if somebody could give me some advise?
My DB is all but complete and have handed it over to the customer to use/trial. I'm quite expecting him to ask for something to moved/adjusted on the screens. I'm quite confident that it does all that he requires and it has been checked it for errors. Not quite so confident as to the layout as Its been a case of guesswork.

I would like to be able to have a way of updating the forms without affecting the data that he has put in as it is live data. I know I could just copy the one hes using, adjust it and send it back or I could inport new forms into the DB but I belive there must be a more efficent way.

 

[DCrake]

You have fell into the trap of not splitting the application in the first place between data and objects. That way you can develop the front end objects without affecting the data or compromising the end users uptime.

Split the database straight away and give him the split version

 

[ddrew]

If I have both parts of the DB in a file C:\ My Documents\ Databases on my PC when I move onto the users PC I m ay put it in a different directory, C:\My Documents\Company Name for instance. Will the front end still be able to find the tables or do I have to change anything?

 

[DCrake]

If it were me I would place the mdb in a folder that is common to both users

C:\Program Files\Databases\FrontEnd.Mdb
C:\Program Files\Databases\BackEnd.Mdb

So when you deploy the front end it will always know where the data is. However if the customer is using a server and you cannot replicate the path then you need to check the links when the mdb opens and relink if need be.

 

[ddrew]

The DB isnt going on a network, its going on to a stand alone laptop. The only reason I wanted to split it was to allow me to develop the front end if need be. Maybe the answer is to carry out the split once I have put it on the users PC.

 

[Zigzag]

C:\Program Files\Databases\FrontEnd.Mdb
C:\Program Files\Databases\BackEnd.Mdb

In my experience placing FE and BE in the same folder tends to slow down the application. Keep the frontend and backend in seperate folders.

 

[ddrew]

OK, thanks for the advise.

 

[DCrake]

ZigZag:

In my experience placing FE and BE in the same folder tends to slow down the application.

Never heard of that before, only in instances where the location is on a server. Never locally, what evidence have you of this?

DDrew:
Why wait till it's on their machine? Do it on yours first, checks that it still works ok in its split mode, then give it to the customer. Some functionality cannot be replicated in split databases. Letting your customer find this out will lessen your professional status.

 

[ddrew]

ZigZag:Why wait till it's on their machine? Do it on yours first, checks that it still works ok in its split mode, then give it to the customer. Some functionality cannot be replicated in split databases.

I go back to my earlier post,

If I have both parts of the DB in a file C:\ My Documents\ Databases on my PC when I move onto the users PC I m ay put it in a different directory, C:\My Documents\Company Name for instance. Will the front end still be able to find the tables or do I have to change anything?

 

[Zigzag]

Dave

I dont have any evidence of this other than experience, but not locally!!!
I usualy run and test on an external hard drive so I don't get a false impression of performance, so it might not apply to a local setup. I think it might fall into the same ethos as 'keep the BE name short' , 'keep the BE as close to the root as possible'

ddrew

If I were you I would...

1, Split the database up FE/BE.
2, Add code that can relink frontend to the backend.
3, Add code to modify the backed table structure from the front end.

Garry

 

[ddrew]

OK thank you for this. Next question is, can anyone give me a clue to the code as I have no idea?

 

[Zigzag]

For the relink code try this

http://www.mvps.org/access/tables/tbl0009.htm

dont miss this

GetOpenFileName

 

[dfenton]

In my experience placing FE and BE in the same folder tends to slow down the application. Keep the frontend and backend in seperate folders.

I've never heard of nor experienced such a thing in 14 years of professional Access development.

 

[SOS]

I've never heard of nor experienced such a thing in 14 years of professional Access development.

And I agree. I've never experienced any problems with a frontend being in the same folder as the backend. However, that being said, normally in a multi user scenario you won't have them in the same folder because one will be on the server and the other SHOULD be on the local machine of the user.