Event when Backend is activated/ldb

A

Aka

Hello,
I was wondering if there is an event I can tap into, or something I can use
to run code, when a front end accesses a back end, from within the back
end. Currently I have a scenario where I run code in the back end, from
the front end when the front end first connects, and it works great. But,
I wondered if I could remove the need to run the code from the front end,
and just have the code in the backend run when it's "activated" or
connected to by a front or essentially at the time when you see the ldb
file created?
Thanks for any info,
Ak
 
D

dch3

Just a bit confused, someone just planted a big sloppy kiss on me, but that's
beside the point...

To my knowledge - no. Plus even if there's a way to do that machine with the
front end would be executing the code even though it resides in the backend.
Access does not have a client-server database and so if anything needs to
happen its going to be on the machine that the user is running. The reason
for using a front end/back end configuration is to allow multiple users
access to the data.
 
A

asdf

Just a bit confused, someone just planted a big sloppy kiss on me, but
that's beside the point...

To my knowledge - no. Plus even if there's a way to do that machine
with the front end would be executing the code even though it resides
in the backend. Access does not have a client-server database and so
if anything needs to happen its going to be on the machine that the
user is running. The reason for using a front end/back end
configuration is to allow multiple users access to the data.
Click to expand...

The creepy sex imagery was weird, but thanks for taking the time to
answer, anyway.
Ak
 
K

Klatuu

There is no such event. Running code in the back end from the front end does
absolutly nothing advantageous for you. The Jet database engine that Access
uses is a File Server database engine.

That is, no code runs on the server. Every line of code including SQL
queries runs on the client's machine regardless of where the mdb files are
located.

In realitiy, all you are doing is slowing down your application. That is
because the user's computer has to load the code module accross the network
before it can execute it. So, your best approach would be to move the code
out of the back end into the front end.
 
Top