Convert Access 2007 to 2003 errors

  • Thread starter Thread starter M Skabialka
  • Start date Start date
M

M Skabialka

I developed an Access database in access 2007 with multiple functions
extracting from and exporting into Excel worksheets. Then I found out the
user was incorrect in thinking they had Office 2007, they have Office 2003,
and had downloaded a converter for Word and Excel 2007 files. I converted
the database to Access 2003 and it runs OK in Access 2007, but on a test
machine with only Office 2003 got multiple errors.
I was able to solve most of the reference problems by manipulating which
references were checked.

But:
Combos do not show any data even though the query in the row source works
fine, even if I create a new combo.

I created and used an Import specification for the Excel data but DoCmd.Run
SavesImportExport "ImportExcel" shows Compile Error "Method or data member
not found".

How do you create a saved import specification in Access 2003?
What could be my combo problem?
Mich
 
M Skabialka said:
I developed an Access database in access 2007 with multiple functions
extracting from and exporting into Excel worksheets. Then I found out the
user was incorrect in thinking they had Office 2007, they have Office 2003,
and had downloaded a converter for Word and Excel 2007 files. I converted
the database to Access 2003 and it runs OK in Access 2007, but on a test
machine with only Office 2003 got multiple errors.
I was able to solve most of the reference problems by manipulating which
references were checked.

But:
Combos do not show any data even though the query in the row source works
fine, even if I create a new combo.

I created and used an Import specification for the Excel data but
DoCmd.Run SavesImportExport "ImportExcel" shows Compile Error "Method or
data member not found".

How do you create a saved import specification in Access 2003?
Click to expand...

That's a new feature in Access 2007, so you won't be able to do your imports
or exports quite the same way in Access 2003. Instead, you'd normally use
DoCmd.TransferSpreadsheet in one way or another.
What could be my combo problem?
Click to expand...

Make sure that the combo box's RowSource query returns the records you
expect. Make sure the original field to which the combo was bound wasn't a
multivalue field (no multivalue fields in Access 2003). If you have service
pack 3 (SP3) applied to Access 2003, see if you are experiencing this
problem:

http://support.microsoft.com/kb/945280/
Combo box controls and list box controls display no value or incorrect
values in Access 2003 after you install Office 2003 Service Pack 3

If that's your problem, there's a hotfix for it. Here's the link:

http://support.microsoft.com/kb/945674
Description of the Access 2003 post-Service Pack 3 hotfix package:
December 18, 2007
 
Back
Top