|
|
Posted by Rico on 04/22/06 08:33
That would be it. I learn something new every day. ;)
Thanks guys!
Just out of curiosity, is there any reason why that is? I wound up
installing a work around for the time being in the form of a stored
procedure, but is there any resource that provides an explanation of that
reasoning?
"Rico" <r c o l l e n s @ h e m m i n g w a y . c o mREMOVE THIS PART IN
CAPS> wrote in message news:zA72g.55411$7a.37458@pd7tw1no...
>I have a data file that I converted from Access to SQL Server using the
>upsizing wizard. I then attached the tables to the Access front end using
>an ODBC connection. I have one table that is read only for some reason.
>I'm not sure how that happened, it went through the same procedures as the
>other tables in terms of upsizing and connecting. The original table was
>not read only or hidden or anything else, it had full permissions.
>
> I've tried disconnecting and reconnecting the table but still the same
> thing. In SQL Server, the permissions are the same as all the other
> tables. I can't seem to figure out what's making this one read only.
>
> I'm using SQL Server 2005 Express and Access 2003. Any ideas would be
> greatly appreciated.
>
> Thanks!
>
>
Navigation:
[Reply to this message]
|