Read the Help on 'Copy TO. ' command.You will see that for Excel 97 and earlier the limit for the number of records is 16,384 and it cannot process files containing more than 32,767 records.
So your 16,000+ outcome for 5.0/95 is explained. I suspect that IMPORT has the same limitation,although it is not mentioned in Help.The 26,000+ records should be handled according to Help. The fact that it is not, suggests that you are hitting another size limit, either in VFP or Excel.I have never tried to import a large number of records, so have no experience of this number of records/rows. All I can suggest is that you divided the Excel file into 2 or 3 files so that it can be handled.The English Bob. Am confused about the 26000+ / 16000+ is this a record number or a computed total within the spreadsheet?If it is a computed total - what happens if you create/copy the entire spreadsheet to a values only spreadsheet and import that?If it is computed - it could be that you have a circular reference within the spreadsheet which is causing the problem.The C000000005 error code within VFP can be caused by a lot of external elements - it mainly is caused by 'memory management' problems.
Like - release of objects and programs. So check that you are closing the Excel interface and its relatedobjects correctly.The English Bob. Read the Help on 'Copy TO. ' command.You will see that for Excel 97 and earlier the limit for the number of records is 16,384 and it cannot process files containing more than 32,767 records. So your 16,000+ outcome for 5.0/95 is explained. I suspect that IMPORT has the same limitation,although it is not mentioned in Help.The 26,000+ records should be handled according to Help. The fact that it is not, suggests that you are hitting another size limit, either in VFP or Excel.I have never tried to import a large number of records, so have no experience of this number of records/rows.
All I can suggest is that you divided the Excel file into 2 or 3 files so that it can be handled.The English Bob.
Microsoft Visual Foxpro 6.0 Download For Pc
The latest SP for any VFP version is the least erroneous. It's recommended, unless it introduces a bug you can't live with. I don't know a bug in VFP8, which got famous for avoiding that SP, so that's a clear YES for SP1.But if you run an EXE compiled with VFP, the runtime must be the same SP level as the VFP version it was compiled with.Windows 2008 server compares to Windows 7 and can run VFP, indeed there is no windows version by now, not running VFP, and even Windows 8 is no exception, just watch out for SMB2 bugs and turn off opportunistic locking,seeBesides this info, there was some hotfix for SMB2 and it may by now also be included in the normal version.
Microsoft Visual Foxpro 8.0 Service Pack 1
Plus it may not catch you at all, if the VFP process you want to establish on the Server is running on it's own, it's merely a concurrent access offiles problem.If you just want to put DBFs on the server, then asking, if VFP runs on Win2008 is the wrong question, as there is no active server component like with SQL Server, it's just the pure data files, still the same caution with SMB2 applies especially for thesefiles.Bye, Olaf.