Generally, companies that are interested in purchasing an ERP system are not looking for blinking field functionality. I really don't think that the capability to have a blinking field will make NAV stand out in comparison to other ERP systems.... :-k
The only place I thought It might be useful was on the old Pre 4.0 versions.
There were many posts about telling the difference between real & test companies. I thought A blinking field on the main menu saying "TEST" would be useful.
IF CurrForm.TxtField.XPOS+CurrForm.TxtField.WIDTH<0 THEN BEGIN
CurrForm.TxtField.XPOS:=CurrForm.WIDTH;
END;
CurrForm.TxtField.XPOS:=CurrForm.TxtField.XPOS-100;
Comments
http://ssdynamics.co.in
PPPlllllleeeeaaaasssseee NNnnnnnnnnoooooooooo!
RIS Plus, LLC
It was even worse when we didn't have breakpoints.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
It came to mind after that post about setting the timerinterval with code.
:evil:
never use it on an editable field.
I think I got this from Nelson Alberto from msbonline back in 2003 or so. :-k
http://www.BiloBeauty.com
http://www.autismspeaks.org
Yes I remember it back then, and it got the same reactions. If you like I can dig it up, and I am sure Erik will gladly donate that post to Luc.
http://ssdynamics.co.in
RIS Plus, LLC
There were many posts about telling the difference between real & test companies. I thought A blinking field on the main menu saying "TEST" would be useful.
But that's about it.
http://www.BiloBeauty.com
http://www.autismspeaks.org
RIS Plus, LLC
What about a marquee?
(TimerInterval: 50)
IF CurrForm.TxtField.XPOS+CurrForm.TxtField.WIDTH<0 THEN BEGIN
CurrForm.TxtField.XPOS:=CurrForm.WIDTH;
END;
CurrForm.TxtField.XPOS:=CurrForm.TxtField.XPOS-100;