|
|
Posted by Razvan Socol on 11/02/06 06:42
Hi, Dave
If you specify dbo.TableName, then Access will dumbly look for the
table username.[dbo.TableName]. Unfortunately, it's a bug in Access,
and I agree with the workaround that mcnewsxp wrote (however, running
sp_changeobjectowner requires at least db_ddladmin and db_securityadmin
priviledges in that database).
Another workaround is to have two tables, one for each user who will be
doing the export. For example, if you want to export the data from
TableName, create a dbo.Temp table and a username.Temp table and copy
the data from TableName in both. Then execute TransferSpreadsheet and
it will get the data from one of the Temp tables, depending on the
current user. I know, it's an ugly workaround, but it works...
Razvan
Dave wrote:
> Razvan...Thanks for the reply. I must have left that part out. Sorry.
> I did try including dbo.TableName. That also doesn't work. Onething
> that I've been talking over with coworkers is Office Versions. The
> Test User account that I used, I also used on an Office 2k3 machine.
> Everyone else is either using XP or 2K. I know that that shouldn't be
> an issue, but right now that's the only thing that's different.
>
> I have to try the Test User account on an XP or 2K machine.
Navigation:
[Reply to this message]
|