DoCmd.TransferSpreadsheet problem in Access2003 (error 3078)

  • Thread starter Thread starter Christophe Niel
  • Start date Start date
C

Christophe Niel

Hi,

I'm using a ADP project file and I'm having a problem with this command :

DoCmd.TransferSpreadsheet _
acImport, _
acSpreadsheetTypeExcel97, _
"dbo.myTable", _
"myXLfile.xls", _
True, _
"mytable1"

It works fine in Access2000, I have no error and the date are imported from
Excel to Access Successfully

When I open the same file with Access 2003, with or without converting it,
this command doesn't work anymore and I have this error (roughly translated,
it's not english):
Error 3078, the Jet database engine could not find the table
'dbo_myTable'. Make sure the name is correct.

If I use "[dbo].[myTable]" the error is '_dbo___myTable_'
I think there is either a bug, or I can't use a "." anymore, and that would
be a big problem, or there is a new way I don't know about to reference a
table.

In some case, I don't have a problem and it creates a table named
"dbo_mytable" in the user schema. (but that's not good either)


Thanks in advance for any information.

Best regards
Christphe Niel
 
Christophe Niel said:
Hi,

I'm using a ADP project file and I'm having a problem with this command :

DoCmd.TransferSpreadsheet _
acImport, _
acSpreadsheetTypeExcel97, _
"dbo.myTable", _
"myXLfile.xls", _
True, _
"mytable1"

It works fine in Access2000, I have no error and the date are imported from
Excel to Access Successfully

When I open the same file with Access 2003, with or without converting it,
this command doesn't work anymore and I have this error (roughly translated,
it's not english):
Error 3078, the Jet database engine could not find the table
'dbo_myTable'. Make sure the name is correct.

If I use "[dbo].[myTable]" the error is '_dbo___myTable_'
I think there is either a bug, or I can't use a "." anymore, and that would
be a big problem, or there is a new way I don't know about to reference a
table.

In some case, I don't have a problem and it creates a table named
"dbo_mytable" in the user schema. (but that's not good either)


Thanks in advance for any information.

Best regards
Christphe Niel

beat your computer with a log than say habalabaha(ho-bu-lo-bu-ho)turn into
Click to expand...
a million dollars!!!
 
Back
Top