Search results

Looks like not many had experience with this. This is what I found. Although my guess it could be due to Progress object file's single-threaded nature. The error message 50 says that Progress Server received a SIGFPE from somewhere and it killed the client. This is really bizzare. When...

I have an ESQL application. All it does is query (Read-only) records from Progress DB. It works well most of the time, but sometimes it just dumps core with a protrace file. Besides this, it does write into the <db>.lg file with the "Floating Point Exception (50) error. Anyone has a clue...

Thats interesting. I have not used -Nv before. According to the docs, this is used as a startup parameter. Since I've not used it before, please pardon my ignorance here, is it absolutely neccesary to use this parameter ? I was under the impression Progress resolved these version numbers and...

Has anyone here tried connecting Progress v9.1C to Progress V7 databases ? (Ofcourse remotely).

I have a monitoring progress programs which runs in an infinite loop(Process A) in the background. This program checks for records matching pre-determined criteria and if found, forks another process B (a background progress session) . Thus spawned progress session is a child process of the...