Dialog Input
Sbhat
Member Posts: 301
Hi Folks,
In the below code when i enter 'T' in my input it returns 3/28/06 instead of todays date. It assumes T for Tuesday. idea how do i get to print Todays date.
w.OPEN('Enter todays date ##1#######');
w.INPUT(1,tdate);
MESSAGE('%1',tdate);
Regards
SB.
In the below code when i enter 'T' in my input it returns 3/28/06 instead of todays date. It assumes T for Tuesday. idea how do i get to print Todays date.
w.OPEN('Enter todays date ##1#######');
w.INPUT(1,tdate);
MESSAGE('%1',tdate);
Regards
SB.
0
Comments
-
Hello Sbhat
I saw this as well today filtering in object designer on t and it would change to tuesday. It stopped doing it now. So I don't know how this happened.
I would set tdate := today as default. That way they don't have to put anything in there.0 -
Hi Rashed,
Unfortunately 'tdate' is a user input and i cannot force it as today. The weird part is tdate is a variable of type 'Date' and i dont understand why it does not like 'T' and considers it as Tuesday instead of Today.
Regards
SB.0 -
Try using this code :
W.OPEN('Enter todays date' + '#1#######'); W.INPUT(1,txtDate); W.CLOSE; IF UPPERCASE(txtDate) = 'T' THEN tDate := TODAY ELSE EVALUATE(tDate, txtDate); MESSAGE('%1',tDate);
Note : txtDate has the data type of text.No future at CPI0 -
Sure you can force it
w.OPEN('Enter todays date ##1#######'); tdate := today; w.INPUT(1,tdate); MESSAGE('%1',tdate);
I would actually report this to MS. It is definitely a bug.
Personally, I don't use dialogs for inputs. They have horrible user interface, and slow performance, in terms that if you have in middle of your routine, other people will be locked out.0 -
If you update your dialogbox every loop, yes it slows down a lot. But if you update the dialogbox less (lets say once every 3 seconds) it doesn't slow down. I always use a slider that I update once every 3 seconds.ara3n wrote:...slow performance, in terms that if you have in middle of your routine, other people will be locked out.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
to Kriki: yes, but this is about Input Dialog box, which is waiting for the user input during the opened transaction. It means same problems like Confirm in transaction... big deadlocks, lock chains etc... :-)0
-
Thanks kine
0 -
:oops: didn't read the code-part in the post of ara3n. I was only thinking about progress bars.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 324 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions

