B
Bill Sturdevant
I am working in Access 2000. I develop applications that
people need to use who sometimes do not have all the
object libraries needed to run my app. I have created a
small 1-form MDE that loops through the references needed
and puts out a message telling them what is missing. I
send this to them prior to giving them the full app and
they can see if they have everything they need. This
works nicely.
BUT, sometimes, they have Access 2002 or 2003. I do not
have the luxury of giving them a copy of either the full
app or the small MDE in anything other than Access 2000.
When they try to open it in 2002 or 2003 they get a
message about the "On Current" causing a problem.
What code can I use to determine right at start up what
version of Access they have so I can alert them in a more
elegant fashion that the version is out of sync with the
program they are trying to run?
people need to use who sometimes do not have all the
object libraries needed to run my app. I have created a
small 1-form MDE that loops through the references needed
and puts out a message telling them what is missing. I
send this to them prior to giving them the full app and
they can see if they have everything they need. This
works nicely.
BUT, sometimes, they have Access 2002 or 2003. I do not
have the luxury of giving them a copy of either the full
app or the small MDE in anything other than Access 2000.
When they try to open it in 2002 or 2003 they get a
message about the "On Current" causing a problem.
What code can I use to determine right at start up what
version of Access they have so I can alert them in a more
elegant fashion that the version is out of sync with the
program they are trying to run?