Messages
Reply
Edit
Delete05:47 pm
3OK1254A6
| From: | Rick Strahl |
| To: | Frits van den Munckhof |
COM has no way to map .NET Long types to a FoxPro type (because FoxPro has no direct matching 64 bit type), so wwDotnetBridge with indirect calls (ie. GetProperty() in your case) fixes up Long values to a FoxPro number value.
General rule: If direct access of properties or method calls don't work, try indirect access via wwDotnetBridge methods - they perform all sorts of automatic fixups for you transparently that often fix problems with standard type assignments. For example, things like GUID, DbNull, byte[] are automatically fixed up to work when with direct COM access they would not.
There's also the ComValue component (loBridge.GetComValue()) which can also be used to set values the other way.
http://west-wind.com/wsdlgenerator/docs/?page=_3481232sd.htm
There might still be others that don't work - I hope those get reported here and I'll see if there are conversions that can be added to automate the process.
+++ Rick ---
Sorry for posting my last question a bit too soon.
I found the solution:
? TRANSFORM(loService.oBridge.GetProperty(loItem,"Balance")) ? TRANSFORM(loService.oBridge.GetProperty(loItem,"TransactionId"))
