i have developed a program from access 2003 using the
packaging wizard.  how do i fix it so it will not work
after a specific date.  (when the next version will be
distributed)

This is probably an easy question, but I haven't found the answer, so
hopefully someone can point me in the right direction.
I have a database developed as Access 2002 developers (SP1).  I used the
packaging wizard to distribute the program.  I am now inconsistently

i'm trying to deploy my MDE file using PDW.  in step five of 7, i specified english as the install languge, but when i clicked next button, the file "accessrt.msi" can't be found on my office 2003 installer.  what could be the problem here.  or is there anyway that i could deploy ...

I have installed Office XP Dev but not Sourcesafe.
When I go into the MS Access development environment's
VBA coding window to work on my application's progs, I
get two noisy messages popping up telling me I have not

So... I'm developing a fairly simple Microsoft Access database for a small workgroup that does not have Access licenses.
I've read that if I purchase the Visual Studio Tools for Microsoft Office System (around $400) I can do this.
My questions, if anyone out there has some ...

I've got a database that is distributed with Access 2000 runtime and it
works great until it is installed on an XP computer. Certain built-in
commands like TRIM(), FORMAT() and DATE() don't work. I get "#NAME" errors
anytime one of these commands are used. If I take the TRIM() ...

We have a small app built in Access with the DB based on
SQL Server to track project issues. I am trying to find
out specifically what I need to buy to allow users
without MS Access on their PC to use the app. MS seems to

This is Access 2000 being runtimed under Access 2002
(XP). A lot said about distributing .MDE files but how do
I generate one of those for my application?
Thanks in advance.

I need to (urgently) convert a large number of existing
Access 97 databases to runtime (standalone) versions.  
We are upgrading our sites however we will have a
transition period with a mix of platforms including:

My app has the option to dynamically change the picture property for a form
(using a file selection dialog to select an image (.JPG) file from anywhere
on disk. I need to use .JPG files (.BMPs are too large).
When the form loads, a progress bar appears briefly saying that the file ...

Can you help with a problem some users of a small app are
experiencing.
I've done a small utility/database using Access 2002 and
used the 'packaging wizard' to prepare the installation

We have an Access 2000 database (with a Visual Basic front-
end) that was compiled and it does not work on the new
machines that came with Office 2003.  What must we do to
make this mde work with Access 2003?

I am just wondering if anyone can help answer my
question.  It has been puzzling me for days now.
I have made an application in Access 2003, and with the
developer tools, I have made a runtime for it.  I

Greetings.  My company is going to distribute the front-end of an
Access application to all users using Access 97 Run-Time.  I am
testing Access Run-Time to see what we gain or lose.  I am no expert
user with Office 97 Developer's Kit, so please bear with me as I

Using the Access 2003 Package Wizard for the first time.
Caching files doesn't work. I'll copy manually accessrt.cab and msi as well
as likely the setp.exe file (for me it is msaccsetup.exe or similar).
I still miss the "base.msi" file that is not on my CD (this is an enterprise