You may not have a choice other than to split them into 2 Integer fields on his end, since I don't think there's an easy way to get VFP to handle getting a 64-bit integer. I hope I'm wrong, and would love someone to correct me.
While you may possibly be able to store it in a 8 byte field, it's not clear that VFP is actually giving you full access to all 64 bits (depending on what field you choose, aka, currency, date, datetime, double, etc...). If VFP is mangling bits or reserving some for it's own use, your stored numbers will likely comeback to his app different than what went in. You might not notice it until you store something larger than a 32bit value either. It should be fairly easy for you to whip up a quick test to find out what will happen. Post back with any success / failures.. -Steve >Not sure if he'll be up for splitting them up. That sounds like a >recipe for disaster (or Vistaster...LOL), because if he wanted a >character field, he would have asked for it. I don't want to split up a >numeric field. Sure, it can be done, but that sounds like asking for >trouble. > >Thanks for the idea, though! It was appreciated! _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
