Calling function not returning as expected...

[sstiebinger]

Ok, so it comes back with the first message if I open a blank form and hit save, if I put in a partnum and no manufacturer, I get the first message, but a record is saved to the table...


If i put in both, I get the second message
Does access perhaps save the record internally when calling the function? That's what appears to be happening as far as I can tell...


Edit note - mis-typed in first try.

[sstiebinger]

I suppose I could use validation at the table level... but I'd prefer to do it at the form level, if possible.

[rpeare]

don't save any records to the table, just work with the message boxes/debug statements until you're getting the correct message.

or attach a sample database with enough data to replicate the problem

[sstiebinger]

Sorry if I wasn't clear... I'm getting the correct messages... the sub and function appear to work... it's just that I've now identified the real issue...

I have 2 fields that are required, partnum and manufacturer...

the problem appears to be that if I put data in just one of those fields Access saves the record before calling the function, thus writing an incomplete entry to the table even before the validation function runs.... if the user continues on and updates the fields then the record is updated, so that's not an issue... but if they get out of the form by some other means, I'll have an improper entry in my table...

This database is a split database with over 100 forms, dozens of queries and dozens of tables... which I didn't design but am tasked with updating and maintaining... figuring out what I need to export to create a sample database that can replicate the issue is a little more than I'm able to commit to right now...
I think for now I'll just leave the replicated code in the individual subs and not move it to a function, as this issue didn't occur until I did that... someday when I have time I may attempt to dig deeper on this...

Thanks for all your help rpeare... if nothing else you've corrected my bad behavior on the string concatenation

At this point, I've just spent too much time trying to fix something that's generally minor in the scope of this project and I simply have to move on, unresolved or not.

[rpeare]

ahh ok, you must be using a bound form? Have you set an index on your table to require both fields? if you do that nothing will remain in the table without the required fields being present. I use unbound forms primarily for this reason, I want to control when/how data is accessed rather than having a partial or inaccurate record.

You may also be able to issue an undo command to remove the unwanted record, you an also play around with the 'before update' property.