relink and update BE

[lution]

Posting this mostly to help me think through the issue but feedback would be appreciated.

I've split my database into front and back-ends. Previously, I had a separate utility that clients would have to run to update the back-ends. I'd like to move that work into my front-end but I'm having a hard time figuring out where.

In the front-end I verify the links between the FE & BE. If I put the BE update stuff before the verify, then it's possible all the updates will fail because the BE isn't in the location where the FE is looking for it.

If I put the BE after the verify, then there if I add a new table, the verify isn't going to be able to hookup the new table and give the user an error (I also exit the application if we reach this point because the FE & BE are inconsistent and I don't want the user to have invalid errors/problems.)

It sounds like I need to split the BE update. Verify the links between the FE & BE. If the link is bad, see if this is a new table and if it is, load it, otherwise have user browse to pick the new location of the BE. This logic won't work if the new table is the first one the system tries to verify (?)

I feel like I'm making this harder than it needs to be.

-Lution

 

[KenHigg]

What do you mean by:

'I had a separate utility that clients would have to run to update the back-ends.'

You have a fe.mdb on the client and the be.mdb on the server. Then this 'utility' was a third .mdb? Is it on the client or the server? And it somehow re-linked the tables in the fe.mdb on the client to the be.mdb on the server?

 

[lution]

Each client has their own FE and BE. To date, I have a 3rd database that the users run once that makes schema changes like adding new tables, changing column names, etc. Its a .accde with VBA code that opens the BE and makes the necessary changes. I'm looking to move the functionality in the 3rd database into my front end so users don't have to remember to run the 3rd database.

Actually, thinking about it while writing this response, I think I can just check my BE version to see if it matches the FE version. If the version of the BE < FE then automatically run the 3rd db to update the BE. When that's done, then verify the tables are synched. If I can't get the BE version, I go through the same flow because I have the user browse to select the BE.

-Lution

 

[KenHigg]

I see. Sounds like you figured out a solution...

Not sure why there is a BE on each client but there must be more than meets the eye

 

[lution]

I have clients scattered across multiple companies so each company has their own FE & BE. When I have updates, usually I just have UI changes so I can deliver a new FE and everything is good. Unfortunately I also occasionally have to change the BE at each company. I used to deliver the 3rd database to do the updates and ask each customer to run it once. Hope that helps explain things.

 

[boblarson]

I have clients scattered across multiple companies so each company has their own FE & BE. When I have updates, usually I just have UI changes so I can deliver a new FE and everything is good. Unfortunately I also occasionally have to change the BE at each company. I used to deliver the 3rd database to do the updates and ask each customer to run it once. Hope that helps explain things.

I don't know if it will help but I have a Backend Auto Update tool which will let you do things to the backend at remote locations. Perhaps it will be of use or, you can take code from it to work in your situation.

You can find it here:
http://www.btabdevelopment.com/main/MyFreeAccessTools/tabid/78/Default.aspx