Command Button Works in 2007 but not 2003

[annie52]

I have both Office 2003 and Office 2007 users accessing a front end on the server from a shortcut on their desktops. The application is nearly a year old now.

Today, I added a new command button on the main menu that does the following:

-- Using a saved import specification, downloads data from a spreadsheet into a temporary (make) table.
-- Compares the data in the temporary table with data already in the database.
-- Displays a report showing those records in the temporary table having no matches in the database.

This works fine for my 2007 users. But, when my 2003 users click on the button, nothing seems to happen.

I'm not sure where to start trouble shooting. Any ideas?

 

[MajP]

http://msdn.microsoft.com/en-us/library/aa830852(office.10).aspx

 

[annie52]

Thanks MajP. I pretty much use those debugging steps in my development (2007) copy. My users don't like to give over their machines and I don't have Office 2003 available to me.

Is there anything wrong with my choice/order of libraries?

MS DAO 3.6 Object Library
MS ActiveX Data Object 2.8 Library

 

[MajP]

When you say nothing happens, I assume that means no error messages or no trapped errors. Therefore, I would not assume a reference issue. If it was a reference issue usually you would get some kind of object error: "object not set.. Object does not support.. etc.)

However, I can not imagine how you could attempt to address this problem without getting on a 2003 machine. On a 2003 machine with simple debugging steps you could at least see what part of the code is firing, what objects are being instantiated, what the values of variables are. That is usually always my first step, lots of debug.print to show what parts of the code are executing.

 

[annie52]

Hi MajP. Of course you are right so I pushed one of my 2003 users a bit harder. I'm getting the old 424 error (object required) at the first line of Case 7:

Case 7
DoCmd.RunMacro "mcrMilstripDelaysImport"
DoCmd.OpenReport "rptMilstripDelaysByNSN", acViewPreview

The macro ("mcrMilstripDelaysImport") does exist and here's what it does:

DoCmd.RunSavedImportExport "MilstripDelaysImportSpec"
DoCmd.SetWarnings False
DoCmd.OpenQuery "qryMilstripDelays", acViewNormal, acEdit

It turns out that the RunSavedImportExport method of DoCmd is new to Access 2007. Can you recommend another way to do this?

 

[MajP]

You should be able to use the Transferspreadsheet method?

 

[annie52]

I just took a look at that. Not sure I really like it though. I think I'm going to try dragging my feet awhile on this. I'm going to bet that we have enough 2007 users willing to run the report for 2003 users when requested. I'll sure be glad when everyone gets updated. Thanks for walking through this with me.