Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 7341 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

im having trouble validating my ID field where i have somewhat of a reoccuring loop which wont let me continue. check out my file. create a new record from the main layout and starting left to right select semester, year, and enter in the Lname field: Johnson. you should see two names pop up for selection.

now if you enter in a last name that is not in my prof database im trying to be able to jump over and enter in the professor information. the only way i can do that now is to delete the record. i have tried some calculation (not isempty) but i still have a little trouble where i have to delete the record to get out of the loop.

please give me any suggestions you may have.

thanx

trytryagain.zip

Posted

A few suggestions: don't allow data entry into serial-numbered fields; set them on commit, not creation; make them numbers, not text; don't validate them (no need to). With these changes, I stopped your recurring loop.

Posted

I disagree that serial numbers should be numbers, you don't do math with them. I agree that the validation for the auto-entered serial number is unnecessary. However I would set the auto-enter to Prohibit modification during data entery and not allow override.

The calculation for the validation of id should be Case ( not IsEmpty ( Lname ) ; not IsEmpty ( prof::id ) ; 1) or Case ( IsEmpty ( Lname ) ; 1 ; not IsEmpty ( prof::id ))

When developing I set the validation allow override. Lets you get out of these loops.

This topic is 7341 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.