Re: MDE and runtime

Just a correction here - I can convert to MDB 2000 but NOT compile to 2000
MDE from 2003. Also, the problem here is not the code compilation in 2003,
but the reference to the Access Object Library in the \Office9, \Office10,
or \Office11 directory. I believe that MSACC.OLB resides in the Office9
folder for Access 2000 but the Office10 folder for Access XP/2002, so I
don't see how compiling to 2000 would not get the user past the error if the
user has Access XP on the workstation. Right now, the problem is that there
is no ...\Office11\MSACC.OLB for an Access 2002 PC, and if I compile to
Access 2000, the problem would be that the user would not have the
....\Office9\MSACC.OLB, since what he does have is ...\Office10\MSACC.OLB.

Is the only solution to keep three development workstations around, one each
of Office 2000 Pro, Office XP Pro, and Office 2003 Pro?

"Brian" <brainy@xxxxxxxxxxxx> wrote in message
news:O1xjmnZYGHA.4424@xxxxxxxxxxxxxxxxxxxxxxx
OK, so I have only Office 2003 Pro installed on my dev workstation,
although I do have access to my prior XP & 2000 Pro CD's. Two questions:

1. I can convert to a 2000 MDB but compile it on my dev PC that has 2003
Pro installed. Wouldn't I run into major version complications if I dig
out my old 2000 Pro CD and install it on my dev PC in order to accomodate
this?
2. Will I lose any functionality in converting from XP/2003 to 2000
format? If so, is there a list somewhere of what I might lose?

"Paul Overway" <paul@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23haf$FaXGHA.1196@xxxxxxxxxxxxxxxxxxxxxxx
Better yet...compile 2000 and don't worry about compiling in newer
versions.

--
Paul Overway
Logico Solutions, LLC
www.logico-solutions.com


"Alex Dybenko" <alexdyb@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OMkA$chVGHA.1348@xxxxxxxxxxxxxxxxxxxxxxx
Brian,
if your clients has versions 2000, xp, 2003 installed - then you have to
install at least Access 2000 and compile MDE using it.

Of course you can also install Access 2003 runtime at each PC. But...
for me is much less problems to ask client what Access version he has
and compile using proper version

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com


"Brian" <brainy@xxxxxxxxxxxx> wrote in message
news:%23KZTR7eVGHA.5916@xxxxxxxxxxxxxxxxxxxxxxx
Yes, but at this point I may be sending the app to clients with nothing
more than a "requires minimum of Access 2000, or else you must install
the included Access 2003 runtime". That is, I may be involved with
clients that simply want to purchase the software with none of my
involvement in (or even knowledge of) their infrastructure. It
certainly makes me look a lot less flexible and knowledgeable if I have
to start asking questions about their Access versions before I send
them a demo version. And since the app is still under development to
some degree, I may be issuing updates on a regular basis for some time
to come. Customers! They keep getting in the way of development... Now,
if I could just keep the customers away, I wouldn't have this problem,
would I?

Is it feasible to simply require all clients to install the Access 2003
runtime package, or will that cause problems for those having
pre-existing Access 2002 or 2000on their computers?

I have Access 2003 with VB Tools, so I have no way to compile to an
earlier version. Or are you saying that I can just convert to Access
2000 format, and then compile MDE, and it will work?

"Alex Dybenko" <alexdyb@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uPTifFYVGHA.4884@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
the trick is to compile MDE on a same Access version, then on a client
PC. Or, at least, you can compile on lowest version number

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com


"Brian" <brainy@xxxxxxxxxxxx> wrote in message
news:O1Be7cNVGHA.1236@xxxxxxxxxxxxxxxxxxxxxxx
The Access Object Library reference (MSACC.OLB) is different for my
dev machine (Access 2003 with VB Tools), where this reference sits in
an ...Office11 folder and clients having Access 2000 or 2002, where
the reference sits in the ...Office10 folder. Thus, my app fails
miserably as an MDE unless it is compiled on a machine having the
earlier version of Access.

Is there any way other than an MDE to keep the 99% of casual pirates
out? Never mind the other 1% that are serious hackers. MDB with
AllowBypassKey = False is too easy to undo; there are several tools
already available to turn this on again.

Is it feasible to simply push out an Access 2003 runtime with EVERY
implementation, or will this mess up existing settings or file
associations when installed on systems that have Access 2000 or 2002
full version installed? Could I even guarantee that the runtime would
be used for my app if I did it this way? (Yes, I do have the VB Tools
for Office and thus the developer tools).

Or, should I just distribute the Office11 Access Object Library to
the appropriate folder during installation so that even the Office10
folks will have the file in the correct location for the reference.

Or...am I just stuck with having to copy the Office10 files to my
hard drive and changing the reference before compiling the MDE for
those having the earlier version of Access?











.

Relevant Pages

  • Re: MDE and runtime
    ... MDE from 2003. ... each of Office 2000 Pro, Office XP Pro, and Office 2003 Pro? ... to install at least Access 2000 and compile MDE using it. ...
    (microsoft.public.access.devtoolkits)
  • Re: MDE and runtime
    ... the trick is to compile MDE on a same Access version, ... machine, where this reference sits in an ...Office11 folder and clients having Access 2000 or 2002, where the reference sits in the ...Office10 folder. ... my app fails miserably as an MDE unless it is compiled on a machine having the earlier version of Access. ... should I just distribute the Office11 Access Object Library to the appropriate folder during installation so that even the Office10 folks will have the file in the correct location for the reference. ...
    (microsoft.public.access.devtoolkits)
  • Re: 2007 Installation
    ... I encountered the exact same problem after installing Access 2007 alongside ... pre-compiled mde. ... The solution is to compile the 2002 mdb into an mde using the 2007 ... I have an exe that opens an Access "portal" ...
    (microsoft.public.access.setupconfig)
  • Re: 2007 Installation
    ... I encountered the exact same problem after installing Access 2007 alongside ... pre-compiled mde. ... The solution is to compile the 2002 mdb into an mde using the 2007 ... I have an exe that opens an Access "portal" ...
    (microsoft.public.access.setupconfig)
  • Re: MDE not possible ?
    ... First compile the MDB and make sure that there are no errors in the code ... before creating the MDE. ... Because of the methode used to compile the database a lot of references ... If your database is in Access 2000 file format (it should say on ...
    (microsoft.public.access.formscoding)
Loading