Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
PhDbase problem with COM Server in Web App
Message
From
02/11/1999 15:42:55
 
 
To
02/11/1999 15:31:15
Tim Godwin
Information Technology Group
Tustin, California, United States
General information
Forum:
Visual FoxPro
Category:
Third party products
Miscellaneous
Thread ID:
00285696
Message ID:
00285701
Views:
15
>I'm using Web Connection as well as phDbase. The VFP app is built as a Single Use COM server. When I load the phDbase.V50 library in the app, the following Windows message appears:
> "memory is low, so streaming output updating has been disabled" and there is a windows dialog box with an OK button. If I press OK everything works fine.
>
>The problem is this is a COM server so that it loads automatically. The COM server runs on the Web Server unattended so there is no one who can press OK. Is there a solution or workaround for this problem? I spoke with Rick at West-Wind and the error message isn't coming from Web Connection. It either must be something in phDbase or Windows itself.
>
>Environment: Web Connection (v. 2.96); VFP 6.0; West-Wind Web Connection 2.96; MS Personal Web Server and IIS 4.0, Windows 95, 98, NT 4.0 Service Pack 4 (the problem occurs using any of these OS)
>
>I've seen this same problem on a couple of threads here and West-Wind's site, but with no solution posted, and I haven't received any reply from the phDbase guys.

This is a common problem in PHDBase. I have found no workaround yet. What I know is that this message will only occur after a while and it won't come after. So, my app is running for about a few hours. Then, I have this message. I press OK and it won't happen again. It will only happen again if you start the app again.

But, this is interesting. On most Web sites I've worked on, we usually isolate the search engine from the main engine. The search engine is usually the most killer feature. So, we isolate it on a separate process. That might help a little bit.

Our search engine is running on the server as well and we have another search robot used to index running on a workstation. We had the problem on the server before. But, now we upgraded the memory and never got it after. As for the workstation, we have the problem. I guess if we upgrade the memory there as well, it will go away.

I talked about this with Jim. No clear answer was given.
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform