>>Hi.
>>I've hit the 2 gig lim on a file in an app
>>It would be a huge job to start splitting up the file , or going to SQL SERVER so i'm trying to identify other options,
>>There arent that many characyer felds that I can reduce, but there are a few numeric fields I could optimise.
>>I have these now set to N 17 2 and would need to allow for 999,999,999.99
>>Whats the Least otimum numeric data type for this ??
>>Also, if there are any other suggestions ?
>
>You can use either currency or double B(2) which both only take 8 bytes in stead of 17.
>Maybe you can store some of the character fields into MEMO fields ?
>
>Better, however is to look for dumping older records into a seperate file though, or find a SQL server strategy. VFP just does not handle files beyond 2 GB..
>
>Walter,

Walter;

Archiving records or going to SQL Server seems like an inevitable conclusion at some point.

There are two ways I have used to Archive – the simple way was to dump to a CD. Creating a separate database was another way. There are lots of unknowns.

As Cindy pointed out if this can be done with a simple change of structure and will suffice then that is the way to go. It might be a good temporary or permanent fix depending upon what is going on.

Tom