Hi Gerard

>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 ?
>

What about city (c35), state/province (c20) and country c(20). To me this is a classic data modelling mistake. This allows entry of Toronto, Ontario, Ireland. Instead you should have 3 tables, City, States, Countries. City is related to state - exceptions exist where city is related directly to country - and state is related to country. This way a single integer city FK could be used and only need 4 bytes instead of 75.

Point being there are likely more ways to normalize your data.