Using VO 2.8 - 2837. Could anyone (Robert if you are there) can shed some
light on the cause of Error Code: 33 [ DATA TYPE ERROR ] ?
This occurs on various sites, but I cannot duplicate the issue my system and
I do a remote web session, I still could not duplicate with the customer
tracing the sequence of operations.
The VOERROR.LOG has an error on a line:
LOCAL dEndDate AS DATE
dEndDate := SELF:oDCmDropdate:Value // ERROR 33 HERE . oDCmDropdate is
DateTimePicker control which exists on a data window.
Error Object created:
--------------------
SubSystem :BASE
SubCode :0
GenCode :Data type error
OsCode :0
ArgType :NIL
FuncPtr :0x0032F655
ArgNum :0
FuncSym :=>DATE
Severity :0
Arg : 14
ArgTypeReq :DATE
SubstituteType :DATE
--------------------
In some other cases, the error was on something like:
LOCAL cValue as STRING
cValue := SELF:Server:FieldGet(#SOMEFIELD) // returns a STRING value
I am suspecting the GC has kicked in at some point, then the values were no
longer valid and thus the error. I did a search on the libraries that I use,
I found the bBrowser 2.0x has several calls for CollectForced() ( I am not
blaming bBrowser), but could those CollectForced() be causing issues in my
application?
Any pointers on what is really going on?
Jamal
use SelecteDate instead of value
Massimo
It looks like they didn’t pick a date so the return from datetimepicker is
NIL.
Regards,
Willie
"Jamal" wrote in message news:ip9fng$r5m$1...@dont-email.me...
I have a Dispatch() which ensures that dates in the DateTimePicker is not
NIL and if it is set it to NULL_DATE (which is valid).
Still not sure about:
cValue := SELF:Server:FieldGet(#SOMEFIELD) // returns a STRING value
When the database was checked, I did not see any invalid characters in the
field; I even did a scan of the DBF via various DBF utilities but they did
not find anything.
I removed all those CollectForced( ) from bbBrowser and any Collect( ) in my
app; I see what happens in the next few weeks.
Thanks!
Jamal
"Willie Moore" wrote in message news:ip9nqe$5cs$1...@speranza.aioe.org...
Thanks for the advice.
Jamal
"Massimo Bighelli" wrote in message news:ip9l99$t9a$1...@speranza.aioe.org...
A pity you don't have a decent error handler to give you the calling
stack etc at this point but no, it is nothing to with the GC. It is
DEFINITELY going to be NIL being send to dEndDate and that is what the
error is telling you. You didn't show us any code so we cannot assist
you with context.
Of course your test for the date's value shows you something because by
the time you test it, it does.
The control's value is NIL or something else at this point.
Geoff
"Jamal" <vodotne...@yahoo.com> wrote in message
news:ip9fng$r5m$1...@dont-email.me:
I have the call stack, I just did not show it. Anyway, I modified the code
to check for NIL, even I set the date to today's date in the window's
postinit( )!
Jamal
"Geoff Schaller" wrote in message
news:4db9e71a$0$77723$c30e...@exi-reader.telstra.net...
>> dEndDate := SELF:oDCmDropdate:Value // ERROR 33 HERE . oDCmDropdate
>> is
>> DateTimePicker control which exists on a data window.
Maybe the returned VALUE is a DATE + TIME which definately isn't a VO DATE
type
CYA
Steve
You are checking for the value BEFORE you assign it.
Using the Postinit may be too late already.
Geoff
"Jamal" <vodotne...@yahoo.com> wrote in message
news:ipemv4$a4u$1...@dont-email.me: