Henry,
We do not have such a problem with 2.5b and we have very large databases. Used on DOS 5 up to Windows XP for years.
Did you tried erasing the index file before reindexing. This is very very efficient. We always do that.
The code would have to be written like this;
CLOSE ALL
ERASE...
To Tonypcq,
The program probably do not hang, it is just too slow to filter the information and it seems like freezing. I have seen that quite often on large databases.
If you ever read this, here is very good trick to eliminate SET FILTER and have super speed performance even on very large...
Thanks to all of you and espacially Tomas, IT WORKS!!
Allocating memory in _DEFAULT.PIF was the answer.
Very simple once we know the answer, as usual.
In fact, I can recreate the situation with windows 98 too; with no memory allocated in the properties the DOS windows just open and closes righ...
Tomas,
I still use the old file names, so everything is 8 caracters left + 3 caracters right.
But, I am thinking of something weird. My application is still as VV.APP - is it possible that it is the problem? Is it possible that Windows XP is waiting for a .exe ??
The latest message I got from...
Hi Tomas,
I like the fact that you said it works with the thirth number in MEMLIMIT and have no problem. I prefer that to limit the maximum memory used.
I also learned since I wrote this posting that DOS programs cannot run on NTFS partitions, only FAT32. Maybe this is the problem with some of...
Hello,
We have a Foxpro 2.5b MS-DOS application that ran flawlesly for years. The 32 bit compiled software works well on windows 95 and up. But with Windows XP we are confused - some users have no problem at all and some others are not even able to start the application. Some others are saying...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.