I'm taking over a large database that has multiple versions of the
front end on the end users machines. What I'd like to do is be able
to run code from the back end when they log in that forces them to
update to the current front end so that I can keep them updated from
then on via the front end.

What I need is some way to make the back end execute code when they
log in.

Is that even possible?

Simply have a table in the fornt end that holds generic program data
such as version number. Create a similar table in the back end that
has version number for that module but also current front end version
number. Then in the front end have code run that tests to see if the
user has the current front end or not. If not, display a message box
and close the front end when the message box is closed. The message
box should tell them they need to update and (if you allow user to do
their own updates) instructions on how to update.

On Mar 26, 12:42 pm, dupuis.mich...@gmail.com wrote:

I'm taking over a large database that has multiple versions of the
front end on the end users machines. What I'd like to do is be able
to run code from the back end when they log in that forces them to
update to the current front end so that I can keep them updated from
then on via the front end.
>
What I need is some way to make the back end execute code when they
log in.
>
Is that even possible?

dupuis.michael@gmail.com wrote:

I'm taking over a large database that has multiple versions of the
front end on the end users machines. What I'd like to do is be able
to run code from the back end when they log in that forces them to
update to the current front end so that I can keep them updated from
then on via the front end.

You can make sure that your front ends have the appropriate code to
check a table in the back end for the version that should be current and
flash a message saying "bzzzt, wrong version, get the latest by..." and
then quit. Put this in either the autoexec macro, or, my preferred
method, the on open event of the start form specified in startup (and
include a cancel = true if the message appears in the latter place.

Or, most elegant and by far the easiest on your users is to get Tony
Toews excellent Auto FE Updater:

http://www.granite.ab.ca/access/autofe.htm

This is perfect if your users will have only one instance of the
application open at a time.

--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Be Careful, Big Bird!" - Ditto "TIM-MAY!!" - Me

You all seem to be missing the point. I have multiple front end
versions, with multiple users. I cannot upgrade the front end code, I
already have a NEW front end that will be put in place via the code
that I need to run from the BACK END.

I need a solution that will run when the BACK END is accessed.

First off you are using a term "code" incorrectly. You cant simply
put the code in the existing front end database. (Not easily anyway
and you really dont want to do that). You want to upgrade users to
the current verision of the front end. This IS accomplished by what
has been suiggested. Maybe you persoanlly cannot go to each users
machine to install the new version but you can wirte a simple script
to do so. Hell a .BET file will work even. However the method to
test for current version is what has been offered to you.

On Mar 26, 3:01 pm, dupuis.mich...@gmail.com wrote:

You all seem to be missing the point. I have multiple front end
versions, with multiple users. I cannot upgrade the front end code, I
already have a NEW front end that will be put in place via the code
that I need to run from the BACK END.
>
I need a solution that will run when the BACK END is accessed.

I will clairfy again. I cannot run a BAT file since I am not the
administrator of the network.
What I need is a way for the Back End to trigger some code (Visual
Basic for Applications) as soon as it's accessed. The VBA code can
then initiate a forced upgrade to the current front end that has
version monitoring and updating code within it.

On Mar 26, 3:15 pm, "DavidB" <j...@yahoo.comwrote:

First off you are using a term "code" incorrectly. You cant simply
put the code in the existing front end database. (Not easily anyway
and you really dont want to do that). You want to upgrade users to
the current verision of the front end. This IS accomplished by what
has been suiggested. Maybe you persoanlly cannot go to each users
machine to install the new version but you can wirte a simple script
to do so. Hell a .BET file will work even. However the method to
test for current version is what has been offered to you.

dupuis.michael@gmail.com wrote:

I will clairfy again.

You do realize this is a voluntary support group and not some customer
support resource where you can pound your fist and demand answers?

--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Be Careful, Big Bird!" - Ditto "TIM-MAY!!" - Me

dupuis.michael@gmail.com wrote:

You all seem to be missing the point.

The only person to have missed the point is you.

The easiest way for you to do this is include code on your front end.
You've rewritten the front end. Good for you. Now put some foresight
into it so that when you do distribute your new front end, you won't
need to worry about users stuck with obsolete versions of it as you find
and fix bugs or develop enhancements.

But for now, you have to find some way to distribute the new front end.
You can't do that via the back end. Again, I would recommend using
Tony Toews FE autoupdater first and the other alternative I and DavidB
suggested second. Email instructions on what to do to get the new front
end running on machines.

Oh... and you're welcome/bienvenue.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Be Careful, Big Bird!" - Ditto "TIM-MAY!!" - Me