Help with Splitting

Colby

New member
Local time
Today, 00:29
Joined
Dec 13, 2005
Messages
105
I have created an application that uses all the 'normal' factors of an access app. My forms are triggered by events that initiate some vba code which executes and then does something. No big whoop, we are all doing this; but I am going freakin' insane keeping up with changes. The users are using this app in a "live" test enviroment and the changes/updates are coming in quicker than I can type. "This field is not right it should read like this"
Well I can't change it until everyone gets out - they don't like this answer:D

I jumped in before thinking a few versions ahead and did not split the database :eek: I have read a lot of posts here and other sites and I can tell that I need to split this app but am a bit hesitant. From what I can gather I would have a
Front-End - houses all my queries and forms
Back-End - houses all my tables

I have a few modules, where would they need to go so that I can work on them independent of what my users are doing?
I would give each user a copy of the FE or make it available via network drive; would I then keep a seperate copy of my FE to make changes? If yes, does this mean my modules would be in the FE?
Can I split the db now that it has been in live production? What are some common errors that I should look for prior to?
I tried to split the db one time before, but my drop down list box(s) on the forms would not work. They are controlled by a query, not any code. Error msg stated could not find xyz sorry I don't recall the exact error

I need the ability to change, work on and update at will AND NOT effect my users.
 
Im gonna type this quick, since I leave work in 15.

FE - Queries, Modules, Forms, Reports, Classes
BE - Tables

Link the FE to the BE with Linked Tables.

Make a Linked table to a control table in the BE with a vesion.
Make a local table in the FE that contains THAT version.

Make thier main form (Dashboard) close the DB if closed (this prevents them from circumventing (accdientally) the update procedure).

NOTIFY THEM OF THIS, have a warning box with a confirm come up when they close the dashboard, most people will just click no and minimize it.

Then, make a OnTimer event in the dashboard that executes VBA that checks the Version in the local table with the version in the Linked Table.

If the Linked Table is Greater than Local, pop up a msg saying thier DB is out of date, and ask them to save thier work, and quickly update the DB by copying the new FE client off the network drive. (Or make an updater db like i did.)

You work on your copy, when a new version is ready for roll out, Increase YOUR COPY'S version, save, compact/fix, overwrite the one on the network drive. Then go into the BE and make the version match the one in YOUR COPY. This will trigger the OnTimer event to interrupt and notify that there is an update pending. Then this will alert your users that they may continue working, but a new update is pending.

If you want, add in functionality for update types, non-critical will let them continue working, and critical will FORCE them to update before doing anything else.

It cannot be seamless, but it's nice if your program politely lets users know that new upgrades have been made and it's in thier best intrest to take 20 seconds to copy the new version from the network.
 
ReAn, thank you so much for the response and the detail. I will start working on this today if the gods decide to smile my way. The instructions you provided seem extremely clear and I only hope it goes as well the instructions. I will let you know how it turns out and/or any bumps I encounter.

BTW, you have helped me out with numerous threads and the 20/hr you stated on a prior post is well below what your knowledge is worth =).

Thanks again.
 
Last edited:
Colby said:
ReAn, thank you so much for the response and the detail. I will start working on this today if the gods decide to smile my way. The instructions you provided seem extremely clear and I only hope it goes as well the instructions. I will let you know how it turns out and/or any bumps I encounter.

BTW, you have helped me out with numerous threads and the 20/hr you stated on a prior post is well below what your knowledge is worth =).

Thanks again.

Hehe, Thanks. Unfortunately it's hard to find much better w/o a degree. I am currently working on that right now ~_^
 

Users who are viewing this thread

Back
Top Bottom