ADP Cannot update table, but Enterprise Manager can!

[dp]

Anyone have any reason why I can open a table in SQL Enterprise manager,
return all rows, and edit the record set, but when I go in through an ADP,
connect to the database, and try to edit the same table, it tells me that
the table is read only. What gives? There are other tables in this
database that I'm able to modify just fine.

-B

[Fletcher Arnold]

"dp" <no****@mrspam. com> wrote in message
news:Xt******** ***********@nwr ddc01.gnilink.n et...

Anyone have any reason why I can open a table in SQL Enterprise manager,
return all rows, and edit the record set, but when I go in through an ADP,
connect to the database, and try to edit the same table, it tells me that
the table is read only. What gives? There are other tables in this
database that I'm able to modify just fine.

-B

Does this table have a primary key? If not, you will not be able to update
via the adp.
Fletcher

[Steve Jorgensen]

On Mon, 12 Jan 2004 16:55:00 +0000 (UTC), "Fletcher Arnold" <fl****@home.co m>
wrote:

"dp" <no****@mrspam. com> wrote in message
news:Xt******* ************@nw rddc01.gnilink. net...

Anyone have any reason why I can open a table in SQL Enterprise manager,
return all rows, and edit the record set, but when I go in through an ADP,
connect to the database, and try to edit the same table, it tells me that
the table is read only. What gives? There are other tables in this
database that I'm able to modify just fine.

-B

Does this table have a primary key? If not, you will not be able to update
via the adp.

Just to clarify and be nit picky, that actually applies only when updating via
recordsets. If you execute a SQL update statement from an ADP by running a
stored procedure or an ADO Command, updating works.


Fletcher

[Fletcher Arnold]

"Steve Jorgensen" <no****@nospam. nospam> wrote in message
news:6n******** *************** *********@4ax.c om...

On Mon, 12 Jan 2004 16:55:00 +0000 (UTC), "Fletcher Arnold" <fl****@home.co m> wrote:

"dp" <no****@mrspam. com> wrote in message
news:Xt******* ************@nw rddc01.gnilink. net...

Anyone have any reason why I can open a table in SQL Enterprise manager, return all rows, and edit the record set, but when I go in through an ADP, connect to the database, and try to edit the same table, it tells me that the table is read only. What gives? There are other tables in this
database that I'm able to modify just fine.

-B

Does this table have a primary key? If not, you will not be able to updatevia the adp.

Just to clarify and be nit picky, that actually applies only when updating

via recordsets. If you execute a SQL update statement from an ADP by running a stored procedure or an ADO Command, updating works.

I imagined the OP was trying to update the table directly in the database
window - but, true, that wasn't explicitly stated. Perhaps we will get some
feedback ideally of the form "Thanks - that fixed it".

Not directed at any specific instance, but just as a comment:
If there is one thing that discourages me from posting (more than the
in-fighting and ugly squabbles which occasionally break out) it is the lack
of feedback from OP's. "Thanks in advance" is nowhere near as good as
"Thanks - that fixed it". A large percentage of the time, you never even
know if your advice was even read - let alone heeded - let alone
appreciated.
</rant>

Fletcher

[Steve Jorgensen]

On Mon, 12 Jan 2004 22:38:44 +0000 (UTC), "Fletcher Arnold" <fl****@home.co m>
wrote:

"Steve Jorgensen" <no****@nospam. nospam> wrote in message
news:6n******* *************** **********@4ax. com...

On Mon, 12 Jan 2004 16:55:00 +0000 (UTC), "Fletcher Arnold"<fl****@home.c om>

wrote:

>
>"dp" <no****@mrspam. com> wrote in message
>news:Xt******* ************@nw rddc01.gnilink. net...
>> Anyone have any reason why I can open a table in SQL Enterprisemanager, >> return all rows, and edit the record set, but when I go in through anADP, >> connect to the database, and try to edit the same table, it tells methat >> the table is read only. What gives? There are other tables in this
>> database that I'm able to modify just fine.
>>
>> -B
>
>
>Does this table have a primary key? If not, you will not be able toupdate >via the adp.

Just to clarify and be nit picky, that actually applies only when updating

via

recordsets. If you execute a SQL update statement from an ADP by running

a

stored procedure or an ADO Command, updating works.

I imagined the OP was trying to update the table directly in the database
window - but, true, that wasn't explicitly stated. Perhaps we will get some
feedback ideally of the form "Thanks - that fixed it".

Oh, don't get me wrong. I was agreeing with your reply, and I'm certain it is
the appropriate answer in this case. I just wanted to add, for posterity,
that in the rare case where you may want to update a back-end table from and
Access app only via a stored procedure ot Insert/Update statement, a primary
key is not a requirement.
Not directed at any specific instance, but just as a comment:
If there is one thing that discourages me from posting (more than the
in-fighting and ugly squabbles which occasionally break out) it is the lack
of feedback from OP's. "Thanks in advance" is nowhere near as good as
"Thanks - that fixed it". A large percentage of the time, you never even
know if your advice was even read - let alone heeded - let alone
appreciated.
</rant>

Agreed. After providing assistance, it's nice to get feedback on whether that
was helpful.