Re: Error in docmd.transferspreadsheet?

Tech-Archive recommends: Fix windows errors by optimizing your registry

give us the exact code; the exact name of the spread***.

are you pushing it into a single range?

you just need to give us more details; buddy

-Aaron


Tore wrote:
I have tried all of your suggestions without any success at all. I have the
same problem on 2 different SQL Server 2000 databases, with the customer and
at the home office. I have never tried SQL Server 2005 because the customer
does not want to upgrade at the moment. I am not able to import to an
existing table or a new table on SQL Server 2000 from Access 2003 project,
only from Access 2000 project.

I have an Access 2000 project on my old laptop. I connect it to the SQL
Server 2000 database on another PC and it works fine. Import is possible via
menu File->Get External data->Import. I get a number of trace-lines on the
SQL Profiler.

I try to do the same thing from Access 2003 project on the same machine as
the SQL Server 2000 database. I get an error from the import spread***
wizard stating "An error occurred trying to import file ........ The file was
not imported" I get only one single line on the sql profiler. EventClass =
SQL:BatchCompleted , TextData =
select object_name(id), user_name(uid), type, ObjectProperty(id,
N'IsMSShipped') from sysobjects where type in (N'U', N'S') and
permissions(id) & 4096 <> 0

When I run the sql from profiler in the sql query analyzer it gives an output:

sysobjects dbo S 1
sysindexes dbo S 1
syscolumns dbo S 1
systypes dbo S 1
syscommentsdbo S 1
sysfiles1 dbo S 1
syspermissions dbo S 1
sysusers dbo S 1
sysproperties dbo S 1
sysdepends dbo S 1
sysreferences dbo S 1
sysfulltextcatalogs dbo S 1
sysindexkeys dbo S 1
sysforeignkeys dbo S 1
sysmembers dbo S 1
sysprotects dbo S 1
sysfulltextnotify dbo S 1
sysfiles dbo S 1
sysfilegroups dbo S 1
Table1 dbo U 0
trace dbo U 0
Table2 dbo U 0
dtproperties dbo U 1


Tore

.

Quantcast