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

A very temporary solution if the number of incoming records (or net gain on records if deletions are permitted) is big enough. I had to go to SQL Server for one of my main apps that dealt with individual transactions as we generate over 60 thousand a day in that particular table. When the file was at about 1.5Gb I did the change of code (not too difficult) and we switched. The original design we were told to do was for less than a thousand records a day. You have got to trust your customers as they know their stuff, don't they.