In this instance I do need a process variable as it is passed via a
column map in a rowset - I want to avoid having to call
idp.utils.GetConcordanceFieldPtr in the rowset loopback as this will
slow things down.
Buried at the bottom of the release notes it says not to attempt to
share pointers with 4D yet, this is a known issue.
If I don't attempt to declare the pointer in A4D, the line
vConcordanceFldPtr := idp.utils.GetConcordanceFieldPtr // return
a pointer to the current language field
executes successfully and A4D makes vConcordanceFldPtr a pointer.
Is this likely to break?
Thanks, Michael.
On 30 Sep 2005, at 14:20, Aparajita Fishman wrote:
I have the following process variable (the only one) declared in
an active4D script
C_Pointer(vConcordanceFldPtr)
vConcordanceFldPtr := idp.utils.GetConcordanceFieldPtr // return
a pointer to the current language field
Running in intepreted is fine but in a compiled database Active4D
brings up the following error:
"C_Pointer(vConcordanceFldPtr)
Expecting a variable or a collection item."
According to the docs we can create process variables "on the
fly". Even if this variable is defined in the compiled database I
still get an error.
Anyone any suggestions?
Buried at the bottom of the release notes it says not to attempt to
share pointers with 4D yet, this is a known issue.
But you don't need a process variable, a local should work.
Regards,
Aparajita
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoylibrary.com
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
