They could still consider splitting the file. Please, note that it could be done 2 ways, either by records (e.g. chronologically) or by fields (move some fields to new related one-to-one table).

>Hi Edward
>
>This was requested by customer who thought that by using varchar they could reduce the table file size.
>
>The reason for wanting to reduce the filesize was because the file sizes are enormous and the 2 GB filesize limit in Foxpro could be a problem. I am aware that the file could be split up, but the customer doesn't want this. I also realise that another solution would be to scale up to SQL server, but again the customer doesnt want this.
>
>>>
>>>The character fields are only part full, is they any way to save space?
>>>
>>Do you have real problems with disk space? Generally speaking, if your database is structured properly then half-empty character fields should be the least concern. Maybe you can split this field on two or more and/or use related table, but I would not recommend using memo just because you want to save space. Memo is used when you want to keep more than 255 characters.