Issue with Windows 2000 and ADP

  • Thread starter Thread starter Drew
  • Start date Start date
D

Drew

I have an ADP that I developed for reporting from SQL Server. The ADP file
is located on the network, and is accessible from the Intranet. When the
ADP is opened, a form pops up with a dropdown that displays names for the
report. The user selects a name and clicks Get Report. Then the report
loads. On Windows XP, the app works just fine, and displays the names in
the dropdown, however on a Windows 2000 machine, the dropdown box is
unpopulated. Only 2 users currently have access to this, since we are in a
testing phase, and the 2 users are in the same group with the same
permissions all the way through. Any ideas or advice?

Currently I have not tested this on any Windows NT machines here, but will
be this afternoon.

Thanks,
Drew Laing
 
Make a private copy of the ADP file for the Win2000 users, checks the
reference in the VBA window and recompile all the stuff. Same thing for
WinNT.

S. L.
 
I'm not sure if I'm following you, please explain? I have been working with
ASP and SQL Server for years, but am completely new to Access ADP's (a
little access experience, I like to think I skipped over the little stuff
and headed for the good stuff, SQL Server)

Thanks,
Drew
 
Sure: Access' ADP and MDB' forms are compiled the first time they are used
and this compilation if not really independant of the underlying operating
system (version, latest installed service pack number, etc.). Each
operating system (and even better, each machine) should have its own private
copy of your application ADP file.

When you want to install a new version of your application to another
operating system, you should copy the file, open the VBA window and then the
References window, make sure that there is no missing reference (if yes,
then make the necessary adjustment) and then force a recompilation of all
modules & forms. There are two ways of doing this:

1- add a dummy (unused) reference in the References window; close the window
(- important - do not skip this step); then re-open it and remove the dummy
reference. After that, from the Debug Window, choose the option Recompile
All Modules. Access will notice the change in references and will recompile
all modules & forms.

2- Or create a shortcut and use the parameter /decompile.

S. L.
 
Thanks for the post and clarification, I will try this and see what happens!

Thanks,
Drew Laing
 
After working with your solution something else popped into my head. I have
done this with another DB I developed, I developed the ADP using Windows XP,
but Windows NT users are using it without a hitch. Maybe I just have to do
it for Windows 2000, but that goes against most of our standard knowledge
now, usually Windows XP doesn't get along with NT, but gets along fine with
2000 (usually). This is a really weird problem, I will try your solution
and see what happens.

Thanks,
Drew
 
Back
Top