On Fri, Jul 18, 2008 at 12:50 PM, MB Software Solutions General Account <[EMAIL PROTECTED]> wrote: > Stephen Russell wrote: >> On Thu, Jul 17, 2008 at 1:08 PM, MB Software Solutions General Account >> <[EMAIL PROTECTED]> wrote: >>> A 3rd party who's writing a DotNet product that will interact with our >>> VFP9 free table app is request us to make a field that is an 8 byte (64 >>> bit) integer. Apparently the -2bil to 2bil that Integer represents is >>> not enough for him. My colleague says that it looks as though Currency >>> type would be sufficient. I wanted to throw this out to the community >>> here to get your thoughts on that. >>> >> >> tell them to convert it on their side. >> >> Convert.ToInt64() >> >> >> >> > > No, he's going to want to store something in those VFP9 free tables, so > that's not gonna be the fix. ----------------------------------------------------
I have friendlyids that won't fit into the int data type as well. they translate to barcodes in use here. But it keeps them unique ;) I have them in multiple columns as well. -- Stephen Russell Sr. Production Systems Programmer Mimeo.com Memphis TN 901.246-0159 _______________________________________________ Post Messages to: ProFox@leafe.com 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.
