11/26/2024 1:24:27 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss usage & tips for SalesLogix controls and other 3rd party ActiveX controls. View the code of conduct for posting guidelines.
|
|
|
|
DateTimeEdit Control in 6.2
Posted: 21 Jun 06 12:11 PM
|
fiogf49gjkf0d I have set several DateTimeEdit fields and Edit Fields in the Properties tab to be a required. Upon testing the required fields I noticed that none of my DateTimeEdit field validations were working. I have two other Edit Fields that are required and work as expected. The DateTimeEdit fields fail to display a validation error or place a red dot next to the required field.
The Question is this. What else I do I need to do to make the DateTimeEdit field a required field and force the user to enter a date?
|
|
|
|
Re: DateTimeEdit Control in 6.2
Posted: 21 Jun 06 1:45 PM
|
fiogf49gjkf0d Personally I gave up on required fields a long time ago. AXFormValidation is where I put all of my form validation. What I do is build an error string based on the number of controls that are missing or have incorrect values and then display it. It's usually something like "The following fields are missing: Type and Status". I've had all sorts of hell with the required fields in 6.1 and since I developed a routine that was good enough, I've yet to see if any of my original gripes are still there.
I also make every DateTimeEdit control read only, forcing everyone to use the calendar pop up. This keeps people from putting in dates like 06/06/2006 where they expect that to be in european dd/mm/yyyy format when in actuality it should be mm/dd/yyyy format. Some people take a "I'll let you color outside of the lines but I'll erase any stray marks" approach whereas I take a "I'll only give you a canvas size of the lines so you aren't even allowed to color outside of them. And yes I may get the lines wrong so that your chimpanzee looks like a baboon but at least it's still a monkey". If the data requirement is for a monkey, chimpanzees or baboons created by users are nice but offer no added value to the data.
The thought is that by giving people less of a chance to screw up, they generally make less mistakes. Regarding your question do you have the Text property bound? Contrary to popular belief, SalesLogix tends to "prefer" text properties over other bindable properties so it's usually a good idea to bind to text whenever possible (at least in my experience). I'm sure with enough testing you could figure out all of the quirks of binding other properties but it's usually a no-test situation when I bind to text. |
|
|
|
Re: DateTimeEdit Control in 6.2
Posted: 21 Jun 06 3:55 PM
|
otc inhalers for copd rescue inhaler otc online fiogf49gjkf0d Hi Jeremy,
Yes these fields are bound. Incidentally I found one of your posts on this very subject (I should have dug deeper this morning) and found that it fit my application to a "T". You have posted a custom AXFormValidation function. I made some changes to it to fit my needs and it works like a charm.
Thank you for your quick post and solution
Regards,
Kevin |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|