G
Guest
ADP 2003 – SQL Server 2000
Catch 22?
I have a form where I want to have underlying record source of a single
record. The stored procedure used for the record source is expecting an
EventId (which is an Identity Seed re: Autonum column). This works great for
existing records.
The problem comes into play for new records. The EventId passed to the
stored procedure is 0 (indicating a new record) and once the user clicks on a
“Save†button, I perform the DoCmd.RunCommand acCmdSaveRecord command.
This causes a 30014 error which states the record is added but does not
qualify for the underlying record source. I think the problem here is that
the record source is for EventId 0 and the autonumm has just been assigned
by SQL Server. After an add I change the record source to the new EventId in
the AfterUpdate Event.
If I ignore the error or trap the error I do not have access (pardon the
pun) to the generated EventId in order to reset my recordsource. Also the
error causes the AfterUpdate event NOT to fire.
I swear that I do the exact same thing in another adp, successfully I might
add but I cannot find a difference!
Anyone have any experience with this 30014 error? Any clue as to what I may
be doing wrong?
30014 - 'The data was added to the database but the data won't be
displayed in the form because it doesn't satisfy the criteria in the
underlying record source.'
Catch 22?
I have a form where I want to have underlying record source of a single
record. The stored procedure used for the record source is expecting an
EventId (which is an Identity Seed re: Autonum column). This works great for
existing records.
The problem comes into play for new records. The EventId passed to the
stored procedure is 0 (indicating a new record) and once the user clicks on a
“Save†button, I perform the DoCmd.RunCommand acCmdSaveRecord command.
This causes a 30014 error which states the record is added but does not
qualify for the underlying record source. I think the problem here is that
the record source is for EventId 0 and the autonumm has just been assigned
by SQL Server. After an add I change the record source to the new EventId in
the AfterUpdate Event.
If I ignore the error or trap the error I do not have access (pardon the
pun) to the generated EventId in order to reset my recordsource. Also the
error causes the AfterUpdate event NOT to fire.
I swear that I do the exact same thing in another adp, successfully I might
add but I cannot find a difference!
Anyone have any experience with this 30014 error? Any clue as to what I may
be doing wrong?
30014 - 'The data was added to the database but the data won't be
displayed in the form because it doesn't satisfy the criteria in the
underlying record source.'