We use files of identical structure and relationship to archive to. The user archives a record and all of its associated records get moved to the archive location. In the app, the active file is searched first and if the record is not located, then the archive file is searched. The active records are shown by default in grids, etc but we include a 'view archives' option and a means to restore from the archive or reactivate a record.


>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