Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 302 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Weird Character Behaviour
Mauddib
Member Posts: 269
Fixed an issue in my company but would love to find a theory on what caused the issue.
We have code from a 3rd party in a report (Nav2017). And we have cloned that report to use ourselves a slightly different way. Our cloned report has not been changed in any way since 05.03.18.
In both reports is a function which replaced the value 0 (zero) in text with the null character 'Ø' as follows:
//NullChar[1] := 157;
NullChar := 'Ø';
OutText := CONVERTSTR(InText,'0',NullChar);
And it has been working this way for years. However today, for no reason I can find, text coming out of this function had the yen symbol (¥) instead of the null symbol.
Tried everything I could think of to fix this until I just hit F11 on the object and it worked as normal again.
What makes this weirder, for me, is the original report (the one we cloned it from) did not have this problem. If BOTH objects had the problem and recompiling BOTH solved it, that might feel like it made more sense! But why one would have the issue, and the other not, I can not explain!
Interestingly if we DEBUG the code then when the debugger starts we see the code in the function as:
NullChar := 'Ø';
When the debugger actually ENTERS the function however, the code suddenly changed to:
NullChar := '¥';
Since the F11 recompile however this does not happen any more.
Any theories welcome, I am baffled!
We have code from a 3rd party in a report (Nav2017). And we have cloned that report to use ourselves a slightly different way. Our cloned report has not been changed in any way since 05.03.18.
In both reports is a function which replaced the value 0 (zero) in text with the null character 'Ø' as follows:
//NullChar[1] := 157;
NullChar := 'Ø';
OutText := CONVERTSTR(InText,'0',NullChar);
And it has been working this way for years. However today, for no reason I can find, text coming out of this function had the yen symbol (¥) instead of the null symbol.
Tried everything I could think of to fix this until I just hit F11 on the object and it worked as normal again.
What makes this weirder, for me, is the original report (the one we cloned it from) did not have this problem. If BOTH objects had the problem and recompiling BOTH solved it, that might feel like it made more sense! But why one would have the issue, and the other not, I can not explain!
Interestingly if we DEBUG the code then when the debugger starts we see the code in the function as:
NullChar := 'Ø';
When the debugger actually ENTERS the function however, the code suddenly changed to:
NullChar := '¥';
Since the F11 recompile however this does not happen any more.
Any theories welcome, I am baffled!
0
Answers