Record deleting in Linked Tables

[Guest]

Hi,

I have an Access database using linked tables to a SQL back-end. On my
client form, I have a button that used to delete the current record being
displayed, but now when clicked I get the error: The DoMenuItem action was
cancelled. In addition to this, existing records cannot be updated. Only new
records can be created.

Can anybody help me out with this problem?? PLEASE.. ANY INFORMATION MAY HELP!

Thanks,
Andrew

 

[Kipp Woodard]

The remote table has to have a unique key defined when it is linked.

 

[Guest]

I do have a unique key already. It's clientID and it's defined as the primary
key in both SQL and Access. Any other suggestions??

 

[Guest]

I already have a unique indentifier, ClientID. It can't accept NULLs and it's
defined as the primary key in SQL and Access. Any other suggestions??

 

[Kipp Woodard]

Can you post the error message? (It is always best to post the text of the
message when posting questions relating to errors).

FYI, most error message dialogs allow you to copy their text. Just make
sure the dialog is selected by clicking inside its borders, then hit ctl-C.
Then you will be able to paste into any text environment.


Kipp

 

[Guest]

When trying to delete a record from the form, I get the error:
The DoMenuItem action was canceled.

When trying to delete a record from the linked table in Access, I get the
error:
The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time.

When trying to update a record, I get the error:
This record has been changed by another user since you started editing it.
If you save the record, you will overwrite the changes the other user made.
Copying the changes to the clipboard will let you look at the values the
other user entered, and then paste your changes back in if you decide to make
changes.
'Save Record' is disables, and I am left with 'Copy to Clipboard' and 'Drop
Changes'.

Updating/deleting and everything else works fine in SQL. It's only in Access
that the problems occur.

-Andrew

 

[Kipp Woodard]

Check out this article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;280730

I had a similar problem with linked tables using a different backend. I
resolved the issue by changing my data-types to simple ones. Instead of
Yes/No (bit), I used Integer.

FYI... you can e-mail me directly if you take the letters NOSPAM out of my
posted addr.

 

[Guest]

Thank you so much!!
This link helped a great deal. What I ended up having to do was simply
change the default value of by Bit types to 0 and to replace all the NULL
fields with 0. Thanks again!