By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,484 Members | 1,811 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,484 IT Pros & Developers. It's quick & easy.

Posting Error

P: n/a
I'm receiving an error whenever the user moves from the main form to a
subform or from the subform to the main form. The problem is, I can't
locate the point within my code where the error is occurring or an
event that occurs before it where I might check for problems; AND it
doesn't even tell me which table the error pertains to.

"The changes you requested were not successful because they would
create duplicate values in ..."

You get the idea. Additional relevant details include the fact that
the subform contains a new record while the master does not. (Leading
me to think that the error is occurring within the subform table.)

Any ideas on how to handle this.
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On 25 Oct 2004 10:42:45 -0700, we*****@verizon.net (Weaver) wrote:

The user is not just "moving". The user is SAVING a record. Or at
least attempting to, and a unique index on some (combination of)
field(s) is preventing it. Probably for good reason, so rather than
removing the index, try to understand what's happening and why.

One tip: most subforms can run as a form by themselves. That's one way
to isolate the problem.

Another one is to realize when a record is saved, such as when a
parent form is dirty and the user moves into the subform -> an
implicit SAVE occurs.

-Tom.
I'm receiving an error whenever the user moves from the main form to a
subform or from the subform to the main form. The problem is, I can't
locate the point within my code where the error is occurring or an
event that occurs before it where I might check for problems; AND it
doesn't even tell me which table the error pertains to.

"The changes you requested were not successful because they would
create duplicate values in ..."

You get the idea. Additional relevant details include the fact that
the subform contains a new record while the master does not. (Leading
me to think that the error is occurring within the subform table.)

Any ideas on how to handle this.


Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.