Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Why VFP9 SP2 stops working?
Message
From
30/09/2017 08:40:29
 
 
To
30/09/2017 04:22:23
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
01654670
Message ID:
01654683
Views:
57
I'd give low probability to VFP exceeding/leaking RAM on 1000 recs - there would have to be collossal blunder in the code called for each record...

Disk space usually a good suspect, but the 1000 ok/1001 fail would make me look at

the driver to the DB (setting some batch border, limit or similar)

and

code in my CA perhaps setting such a boundry and then trying to print a log, measurement or wait for a key and somehow the screen message was obliterated

my 0.02€

thomas

>- Monitor total RAM usage in Task Manager - both overall, and for VFP in particular. If you find VFP usage climbing you can use SYS( 3050 ) to limit it to 500MB or less
>
>- If it's not a production database, check the database's Recovery Model. If it's Full, you could try setting it to Simple. I had one project where I was updating several SQL databases that were in Full recovery mode, and the operations I was doing caused the log files to balloon - ISTR running out of disk space (in a limited-space VM) in one case. Switching to Simple recovery mode addressed that. You could check overall disk space and keep an eye on your log file sizes. If you do switch from Full to Simple mode, bear in mind that reduces your recovery options in case of crashes or other issues, and consider switching back to Full model when you're done
>
>- There's an interesting quirk to SQL Server 2012 and later, that in some cases if you're using Identity columns their values can jump by 1,000 unexpectedly. This is discussed at https://stackoverflow.com/questions/14146148/identity-increment-is-jumping-in-sql-server-database . Interestingly, the top of the first answer has a link to an MSKB article which was up on September 5 when I last looked at it, but has since been taken down by Microsoft. Naoto is right AFAIK, IME there's no row limit in SQL Server Express. On the face of it this issue doesn't seem the same as what you're seeing but the fact it's stopping at 1,000 may not be a coincidence
>
>- You don't say whether you're using T-SQL directly, remote views, or SQL passthrough, but if it's either of the latter you may need to adjust VFP parameters such as FetchSize.
Previous
Reply
Map
View

Click here to load this message in the networking platform