On Oct 3, 2007, at 11:19 PM, David Cottrell wrote: > Jay's method the fastest method - but if I understand correctly (a > big IF) this will also get you into trouble with endian issues if > your data has to move between PPC and Intel. For FBtoC-created applications byte swapping is done if Read# and Write# are used. It uses the strategy of writing everything to disk as big-endian and then doing the swap to host on a read or a swap to big on a write. Read File and Write File do no Endian swapping. AFAIK, an FB-created application has no built-in byte swapping when read# and write# are used. The programmer must make his own calls to the CF byte swapping functions. Harold/Skip - none of this matters if you read/write data on the same computer and you can just ignore it and build on Jay's suggestion. BTW: In addition to David's suggestion, from Apple's Universal Binary Programming Guidelines on swapping bytes: "there are two general approaches for handling byte ordering differences: swap bytes when necessary or use XML or another byte-order-independent data format such as those offered by Core Foundation (CFPreferences, CFPropertyList, CFXMLParser)." Brian S.