Some other options... not always possible but worth considering:
1) remove data of a certain age, putting it into an identically structured table that can be included in (hopefully few) queries that need to process old data.
2) remove "completed" records similarly to above. By 'completed' I mean things like closed accounts or old records in 'balance' or whatever your application can tolerate.

good luck


>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 ?
>
>Regards,
>
>Gerard