Re: Row cannot be located for updating
From: Alverio (alverio.m_at_tiscali.it)
Date: 09/16/04
- Previous message: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- In reply to: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- Next in thread: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- Reply: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 16 Sep 2004 23:56:01 +0200
Both primary keys in MasterTable and DetailTable are Autoincrement field
(Long Integer type). IDMaster, the linking field in DetailTable, is also a
Long Integer. If I set it to Integer, I cannot set the relationship in
Access.
But the problem seems to be on the Primary key fields, as they are not able
to generate the proper increment value when I append a new record.
"Brian Bushay TeamB" <BBushay@Nmpls.com> ha scritto nel messaggio
news:id7jk0pj357qmu8pdr9kf3f53fhb5bt1hg@4ax.com...
>
> >I have a master table and a detail table. Relationship is between field
ID
> >(autoincrement field and primary key in MasterTable) and IDMaster
(numeric
> >field in DetailTable). DetailTable has an autoincrement field as primary
> >key. The relationship is created in Access as well. I'm using
>
> The master linking field in the detail table needs to be of type Integer
to link
> to an Access autoincrment field.
> --
> Brian Bushay (TeamB)
> Bbushay@NMPLS.com
- Previous message: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- In reply to: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- Next in thread: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- Reply: Brian Bushay TeamB: "Re: Row cannot be located for updating"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|