I found out more now:
On my workstation there is no Client for the Server Engine installed, but there is a workgroup engine installed (which should be OK for access to the server engine on the server, no ?)
But on another workstation in our network there is in the opposite _no_ workgroup engine...
I suppose you managed that meanwhile (?)
This is a problem that always confuses me too.
After I set COBDIR, LIB, LBR, PATH to
\COBOL, \COBOL\LBR, \COBOL\LIB it normally works.
Does your Cobol have a copy protection dongle ?
When compiling with that on 2000 or XP it may print
about 100 empty...
We have a long experience calling VB from Micro Focus Cobol. As far as I can say, it worked with VB4 16 Bit and the old 16 Bit Cobol Compiler and it works with 32 Bit Cobol and VB.NET. But there is no way making VB5 or VB6 show non-modal forms when called from Cobol - period.
(The reason is...
> Sounds like you've got two engines opening ... <
Yes, that's what I also think about. However, I don't have any problems using my data on G:\PBA with other applications (that don't use the OLEDB approach), also Function Editor does its job like always, no problem.
Something may be wrong with...
I have a database on a mapped server drive, on G:\PBA
When I connect using Pervasive OLEDB 8.1, after 2 seconds I get an error:
'-4914 File is locked'
The connection string is:
Provider=PervasiveOLEDB;Auto Translate=TRUE;Data Source=GPBA;
Before, in Control Center, I right-clicked onto...
I suppose you will have already solved that problem since that is an old thread, however:
Yes, you must rewrite yous SELECT:
RECORD KEY IS WKN-KEY = WKN-NR-WKG, WKN-NR-WKN
And in the FD you will choose another name for
WKN-KEY, like WKN-KEY-FIELDS (which results in having to do some source...
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.