Re: Can and Can't insert using DAO on SQL Server linked table
From: Mark A. Sam (msam_at_Plan-It-Earth.Net)
Date: 09/05/03
- Next message: Dave Brooks: "BORK 4.5"
- Previous message: tthomson_at_neosinteractive.com: "Re: Strange login attempts"
- In reply to: david epsom dot com dot au: "Re: Can and Can't insert using DAO on SQL Server linked table"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 5 Sep 2003 09:13:11 -0400
David,
It is what I thought also. I don't think Identity Insert is the issue here,
possibly the error message is wrong.
God Bless,
Mark
"david epsom dot com dot au" <david@epsomdotcomdotau> wrote in message
news:evDOfn0cDHA.1032@TK2MSFTNGP11.phx.gbl...
> I think/thought that Identity Insert is supposed to be on
> for only one table at a time in the database. This would
> suggest that there was some odd behaviour that for some
> reason occasionally set identity_insert on this one table.
>
> thanks for your continued feedback
>
> (david)
>
>
> "Synergy" <NoName@NoMail.Com> wrote in message
> news:etX0RmucDHA.1280@tk2msftngp13.phx.gbl...
> > I resolved this issue, but writing a function to delivering the next ID
> > number (to the Identity Field) and assigning it before executing my DAO
> > Update method.
> >
> > This would suggest that Identity Insert was engaged on that table, but
> there
> > was no problem populating other subtables with Identity Fields.
> >
> > God Bless,
> >
> > Mark A. Sam
> >
> >
>
>
- Next message: Dave Brooks: "BORK 4.5"
- Previous message: tthomson_at_neosinteractive.com: "Re: Strange login attempts"
- In reply to: david epsom dot com dot au: "Re: Can and Can't insert using DAO on SQL Server linked table"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|