Verify Front End for expiration

[Guest]

We are building multiple databases for different purposes in the company and
we are splitting each one of them with a front end and a back end. The front
end gets distributed to the corresponding users.

Issues:
When it is time to create an updated front end, we need to make sure the
users are not using the older version anymore as sometimes this could cause
problems: Example: The front end creates a calculation that gets stored in
the database. If the calculation is wrong, then the front end needs to be
changed. And if the user uses the wrong front end, the data will be
inacurate (this is just an example).

How can we make sure the users are not using older versions?
Is there a way to force the back end to check the front end before allowing
connection or before allowing changes to the tables?

Thanks in advance!

 

[Guest]

At this site is an mdb that is used just for that purpose. It is a pretty
neat approach. Basically, it determines if the front end is the current
version and if not, copies the new version and replaces the old version and
reopens as the new version:

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

 

[Guest]

Thanks. This is quite a bit more complex than what I expected, and it looks
like there is no easier aproach.

I will definetly do some research and analysis on this before I can bring it
to production.

Thanks for the help!

By the way: How do you get into this type of job? working with microsoft
to provide assistant to people that need it? Thanks again.

 

[Guest]

In the long run, it is the easiest way.
I did not find it that difficult to fold it into my application.

 

[Rick Brandt]

Thanks. This is quite a bit more complex than what I expected, and
it looks like there is no easier aproach.

I will definetly do some research and analysis on this before I can
bring it to production.

Thanks for the help!

By the way: How do you get into this type of job? working with
microsoft to provide assistant to people that need it? Thanks again.

It's not a job. It's much more serious than that ;-)

 

[Guest]

I missed the bottom part of your post.
As Rick said, it is not a job.
We are all volunteers here. We all use Access and want to see it used to
its maximum capability.
We also realize you can't really learn everything in a vacuum and most of us
don't have coworkers that do the same thing we do.
Microsoft only provided the site, All the answers are provided by people
who just want to help.
I first found this site when I needed help, and over a couple of years, I
think I have learned more that I have taught. A friend of mine once told me
the best way to learn is to teach.

As to a job - I NEED ONE!!! -
my contract expires in about 2 weeks and I have no place to go.

 

[Guest]

You are right. The best way to learn is to teach. Hopefully in a year or
two I'll be knowledgable enough to help others. Thanks for all the help!

 

[Guest]

You probably already know something that someone else does not. Keep reading
the posts. If you find one where you know the answer, respond to it. You
will also learn a lot just reading others' posts.