Hi all,
we are experiencing a weird behaviour in an app here. This is a vfp6
app that performs a series of queries to a MSSQL Server (through odbc),
processes the received cursors and writes a few csv files. This app is
called from a few Progress front ends which then read the csv's and
processes them into the Progress database.
This app behaves properly everywhere (called by Progress front ends or
command line) except when called by a particular Progress front end
where it will return corrupted data (actually a field of the result set
is zero when it shouldn't). Logged the hell out of this vfp app, and
when called with exactly the same parameters from the command line or
when tracing it, the app will behave properly.
I am beginning to suspect there might be a memory corruption problem.
Maybe the Progress front end uses too much memory and corrupts the vfp
app's memory. Anyone ever heard of something along these lines? Any
suggestion/workaround you can think of? Is there any way of
limiting/protecting the memory used by the vfp6 app?
TIA
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
