>>So it isn't the COM spec or standard that is forcing this? So potentially we could ask the FoxTeam to change this?
>
>oops, I think I wasn´t clear. :)
>This issue is outside the domains of the FoxTeam. Look, this came from Randy:
>
>"The only date type supported by COM is VT_DATE. Therefore, in VFP, we have to map our date and datetime types to VT_DATE when creating a COM server. So, this is really a COM issue."
>
>so, for my understanding, if you´re expecting a "date" parameter in your COM server, you'll need to manually remove the "time" part. And, if you´re expecting a "date" return from a method, you´ll also need to treat that manually. :(
That's correct. Generally, pure date type is specific to FoxPro. As Randy said, COM can return only DateTime type. So you may run into situation when you return the date type variable from COM, but receive DateTime instead.
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison