Oh, I was already counting you on, Greg!

Me too!!!

Ivan, I know you have a big beer contest or something like that for the July class, I don't drink beer, but I'll buy you one (yes, just one ) any size you like, if I make it to the class!

Edhy Rijo

Hi Edhy.

You are safe with me, then! I am a very light drinker, but it is going to be a pleasure to have one with you, and just tell me what you prefer instead of the beer.

Hope you can make it. Where are you going to be coming from?

Well, I prefer Steaks and Ice Tea 

I live in New York, so it will be a couple of hours trip, of course I won't drive

Edhy Rijo

Truth be told...we all like to talk big, but everyone (that has posted so far and that I know) including myself, are very light drinkers ...but it is more fun to talk big

Yeah, we actually have people already coming from as far away as Denmark...so I am pretty sure they aren't driving either

No - I'm definitely not driving it is a three flight trip each way. But i have been there before and know the class is worth it and Ivan is buying the beers.

/Teddy

Teddy, I won't even mind if you bring one of those small glasses you showed us.

http://www.ahajokes.com/crt001.html

I don't mean to pour salt into old wounds, but...



I have a question concerning the BO v. control-based validation of value lengths. In apps where essentially all data entry is via forms/controls, maxlength seems like a nice, clean approach. If SF can automatically set (and update when the underlying column widths change) those values based on BOM metadata for us, even better since I don't get any rush setting .maxlength properties these days.



If, however, the app deals with data mining or other importing of external data sans a UI (but using a BO), then the control-based solution is perhaps a bit less of a solution? In my past (VFP/Visual FoxExpress) life as well as my current reincarnation (C#/StrataFrame) it seems I am always dealing with importing of significant amounts of data and I would love to have my BOs deal with whatever it can without requiring my taking time for more complex business logic implementation.



Just interested in everyone's comments on the above... without getting too intense or fanatical... At the end of the day we're all here 'cause we luv SF!!!



Thanks.

________________
_____/ Regards,
____/ al

Hi Alex,

I agreed with you and would also like to see this implemented/managed via the BOM in a near update.

Edhy Rijo

Max length is already on the slate to be implemented at the control level.  The BO already has the field lengths so it is just a matter of implementing logic within controls such as the textbox, etc. to prevent field length issues.  This would obviosuly be a flag that would force the max length.  So this is already on the slate to be implemented.