eTom
Registered User.
- Local time
- Yesterday, 19:27
- Joined
- Oct 15, 2009
- Messages
- 79
Well, originally it was because I couldn't get that code to work. Of course, now it turns out it was a security option issue. Oops.
Now that I've gone to the trouble of creating a second Field in my tables for LotNumberText, I have extra options. We have a few products that don't actually have a LotNumber, just a best before date. I've been making up a lot number based on that date, but with a text field as well I have the option of entering my made up lot number and having the code create a text based version of the actual lot number instead.
Ideally, I could enter 010109 and have the code enter "JAN 01 2009" into the text field for me. I suppose I could have the reports do that function for me too, but if I just have it done at the form level then I never have to worry about remembering to do the formatting whenever I create some new report.
It'll also save me a lot of questions when I present reports. Every time I get asked "but I thought that product didn't have a lot number? Where'd this number come from."
Now that I've gone to the trouble of creating a second Field in my tables for LotNumberText, I have extra options. We have a few products that don't actually have a LotNumber, just a best before date. I've been making up a lot number based on that date, but with a text field as well I have the option of entering my made up lot number and having the code create a text based version of the actual lot number instead.
Ideally, I could enter 010109 and have the code enter "JAN 01 2009" into the text field for me. I suppose I could have the reports do that function for me too, but if I just have it done at the form level then I never have to worry about remembering to do the formatting whenever I create some new report.
It'll also save me a lot of questions when I present reports. Every time I get asked "but I thought that product didn't have a lot number? Where'd this number come from."