>>>I have developed a VSL application in VFP6.0 which has 360 identicaly structured tables (a naming convention of the data transaction date, is used; i. e. xxx990601.dbf) each table contains 24 hours of tranaction data (approximately
>
>>You could run into big performance problems with SQL Server, too. I know we've seen that here with very large DBs. Another approach might be to combine your tables into monthly groupings, so you have 12 tables rather than 360 or so, whether you stick with vfp or move to SQL Server, if that's possible...and same with the 88, combine them into only a few larger tables should help performance.
>
>Thanks to everyone who has taken the trouble to reply and comment. Bruce you are the closest to what I have already discovered with this application.
>Actually the daily tables (I receive them hourly, but combine into daily) are the safeguard to avoid getting close to the 2 GIG limitation (not FoxPro, but WindowsNt limits.)

Doug, with NTFS, you can go lots bigger than 2GB; NT variant FAT16 can go as big as 4GB.