Integrating Paradox with a C++ executable 
Author Message
 Integrating Paradox with a C++ executable

I have Paradox 4.5 and Borland C++ 4.0.
The Paradox manuals don't say anything about how to integrate Paradox
with C++ executables built with Borland's C++ compiler.
Does anybody know the steps necessary to be able to call Paradox
functions from a C++ executable ? Does Paradox have that ability ?
There has to be a way to combine Borland's ObjectWindows
with the Paradox database engine, so that I don't have to write all my
application in OPAL.
Maybe it's something so easy that the Borland manuals don't even care
to mention it. :)

Thanks.



Sat, 23 Nov 1996 03:46:40 GMT
 Integrating Paradox with a C++ executable


Quote:
>I have Paradox 4.5 and Borland C++ 4.0.
>The Paradox manuals don't say anything about how to integrate Paradox
>with C++ executables built with Borland's C++ compiler.
>Does anybody know the steps necessary to be able to call Paradox
>functions from a C++ executable ? Does Paradox have that ability ?
>There has to be a way to combine Borland's ObjectWindows
>with the Paradox database engine, so that I don't have to write all my
>application in OPAL.
>Maybe it's something so easy that the Borland manuals don't even care
>to mention it. :)
>Thanks.

Nope.

It's not possible (Well maybe with a hack...yeah right).  ObjectPAL code is an
iterepted language.

The forms, scipts, libraries you create in Paradox for Windows only hold
object code for another module to drive.  They are not indepent of Paradox.
When you run a form in PW it does something like PDOXWIN.EXE calls PXSRV2.DLL
which calls PXFORM.DLL to control the UI and PXPALEXE.DLL to compile and execute
the ObjectPAL. So you would pretty much have to rewrite PW inorder to accomplish
this hack.  Good Luck.

-joe
--

||   || ||\/|| ||=||   |||     Phone : (408) 425-7455
!!!! !! !!  !! !! !! !!   !!   Fax   : (408) 425-7516



Sat, 23 Nov 1996 11:58:06 GMT
 Integrating Paradox with a C++ executable

As Joe said, can't be done.

Go out and get the Pdox Engine and right the stuff yourself, not all that difficult.

Or, wait a few months for IDAPI (which will supercede the pdox engine) and then write it yourself.

Or, have Pdox as your front end, put the necessary functions in your DLL, then call them from Pdox

--
Beavis kicks ASS! He KICKS 'em! Kicks, KICKS!  He rules, he RULES, RULES!!



Sat, 23 Nov 1996 12:01:44 GMT
 Integrating Paradox with a C++ executable

: I have Paradox 4.5 and Borland C++ 4.0.
: The Paradox manuals don't say anything about how to integrate Paradox
: with C++ executables built with Borland's C++ compiler.
: Does anybody know the steps necessary to be able to call Paradox
: functions from a C++ executable ? Does Paradox have that ability ?
: There has to be a way to combine Borland's ObjectWindows
: with the Paradox database engine, so that I don't have to write all my
: application in OPAL.
: Maybe it's something so easy that the Borland manuals don't even care
: to mention it. :)

: Thanks.

There are 2 methods to do this.  1) Write all of the code in C++ and
use either the exisiting Paradox Engine (a library which allows access
to Paradox) or the IDAPI Engine (another library from Borland).  
The IDAPI engine is the better way to go, but is not available
yet.  2) Do all of your Paradox processing in ObjectPal
and make calls to DLL's that you wrote using C++.  You can call DLL's from
ObjectPal, it's in the manual.
--


Stony Brook, NY 11794



Sat, 23 Nov 1996 20:53:40 GMT
 Integrating Paradox with a C++ executable


Quote:

> I have Paradox 4.5 and Borland C++ 4.0.
> The Paradox manuals don't say anything about how to integrate Paradox
> with C++ executables built with Borland's C++ compiler.
> Does anybody know the steps necessary to be able to call Paradox
> functions from a C++ executable ? Does Paradox have that ability ?
> There has to be a way to combine Borland's ObjectWindows
> with the Paradox database engine, so that I don't have to write all my
> application in OPAL.

There are ways but they're not as direct as you may like.
  1.  Put your functions in a DLL.  OPAL makes it easy to use DLLs.
  2.  Use the Paradox engine and do it all in C++.
  3.  Add DDE or OLE to your C++ program.

------------------------------------------------------------------

University of Colorado  Denver, Colorado
------------------------------------------------------------------



Sat, 23 Nov 1996 22:14:19 GMT
 Integrating Paradox with a C++ executable


: >I have Paradox 4.5 and Borland C++ 4.0.
: >The Paradox manuals don't say anything about how to integrate Paradox
: >with C++ executables built with Borland's C++ compiler.
: >Does anybody know the steps necessary to be able to call Paradox
: >functions from a C++ executable ? Does Paradox have that ability ?
: >There has to be a way to combine Borland's ObjectWindows
: >with the Paradox database engine, so that I don't have to write all my
: >application in OPAL.
: >Maybe it's something so easy that the Borland manuals don't even care
: >to mention it. :)

: >Thanks.

: Nope.

: It's not possible (Well maybe with a hack...yeah right).  ObjectPAL code is an
: iterepted language.

: The forms, scipts, libraries you create in Paradox for Windows only hold
: object code for another module to drive.  They are not indepent of Paradox.
: When you run a form in PW it does something like PDOXWIN.EXE calls PXSRV2.DLL
: which calls PXFORM.DLL to control the UI and PXPALEXE.DLL to compile and execute
: the ObjectPAL. So you would pretty much have to rewrite PW inorder to accomplish
: this hack.  Good Luck.

ObjectPAL is a compiled language which uses run-time DLLS.  ObjectPAL is
not interpreted at run-time.

  -- Dave R.



Sun, 24 Nov 1996 03:48:44 GMT
 Integrating Paradox with a C++ executable


Quote:
>: The forms, scipts, libraries you create in Paradox for Windows only hold
>: object code for another module to drive.  They are not indepent of Paradox.
>: When you run a form in PW it does something like PDOXWIN.EXE calls PXSRV2.DLL
>: which calls PXFORM.DLL to control the UI and PXPALEXE.DLL to compile and execute
>: the ObjectPAL. So you would pretty much have to rewrite PW inorder to accomplish
>: this hack.  Good Luck.
>ObjectPAL is a compiled language which uses run-time DLLS.  ObjectPAL is
>not interpreted at run-time.


text and complied binary code that serve as a DLL.  If the designed modified
byte is set it will force a recompile, or if a new internal version of

compiled DLLs with out source text.  But in reality you are just building
libraries to be run by PW.  But how ever you want to look at it ObjectPAL
is not a "stand-alone" compiled language, and the link libraries creates
can be called by any other language.

-joe
--

||   || ||\/|| ||=||   |||     Phone : (408) 425-7455
!!!! !! !!  !! !! !! !!   !!   Fax   : (408) 425-7516



Sun, 24 Nov 1996 08:00:51 GMT
 Integrating Paradox with a C++ executable

Quote:
>compiled DLLs with out source text.  But in reality you are just building
>libraries to be run by PW.  But how ever you want to look at it ObjectPAL
>is not a "stand-alone" compiled language, and the link libraries it creates
>can be called by any other language.

^^^^^^^

Sorry the key word is NOT ....

-joe
--

||   || ||\/|| ||=||   |||     Phone : (408) 425-7455
!!!! !! !!  !! !! !! !!   !!   Fax   : (408) 425-7516



Sun, 24 Nov 1996 10:10:23 GMT
 Integrating Paradox with a C++ executable

Quote:
>...  But how ever you want to look at it ObjectPAL
>is not a "stand-alone" compiled language, and the link libraries creates
>can be called by any other language.

>-joe

OK. But is there a way to know how to call these libraries ?
And if I could find the names of the functions, I still would not be
able to know what they really did. Am I right ?
Does Borland have a product that lets you call the forms /
reports / queries ... etc.. from a standard C++ code executable ?

It seems that once you have started creating forms and reports with
Paradox you are restricted to use Paradox to do the user
interface flow of your application as well (by coding it in
ObjectPal). I wanted to be able to open up forms and reports from an
ObjectWindows executable.

                        Carlos Gonzalez.



Sun, 24 Nov 1996 23:44:06 GMT
 Integrating Paradox with a C++ executable

Quote:

> Or, have Pdox as your front end, put the necessary functions in your DLL, then > call them from Pdox

... or use Microsoft MFC 2.0 and access 2.0 and read the paradox tables using
access and C++ without the paradox engine or ...

just another of many possible solutions ...

g.mo
--

__

-----------------------------------------------------------------------

Morris Myers                            [Standard Disclaimer]




Sun, 24 Nov 1996 22:06:51 GMT
 Integrating Paradox with a C++ executable


: >ObjectPAL is a compiled language which uses run-time DLLS.  ObjectPAL is
: >not interpreted at run-time.


: text and complied binary code that serve as a DLL.  If the designed modified
: byte is set it will force a recompile, or if a new internal version of

: compiled DLLs with out source text.  But in reality you are just building
: libraries to be run by PW.  But how ever you want to look at it ObjectPAL
: is not a "stand-alone" compiled language, and the link libraries creates
: can be called by any other language.

Your original statement said that ObjectPAL is an interpreted language.
This is not true and thus my reply.  I did not claim that PdoxWin compiled
a "stand-alone" result, in fact, I said it uses runtime DLLs.  I am
therefore perplexed at your response.  You are attempting to agree with
my statement, right?

  -- Dave R.



Wed, 27 Nov 1996 10:36:37 GMT
 Integrating Paradox with a C++ executable
Hi Carlos!
c>
c>OK. But is there a way to know how to call these libraries ?
c>And if I could find the names of the functions, I still would not be
c>able to know what they really did. Am I right ?
c>Does Borland have a product that lets you call the forms /
c>reports / queries ... etc.. from a standard C++ code executable ?
c>
You can send message to paradox forms. Use postmessage(HWnd, wm_command,  
userMenu+myMenuEvent,0) (Pascal syntax). And in OPal use  
winPostMessage(..). Data transfer can be realized via DLLs (for example  
the window handle, the userMenu constant,...).

Gruss, Andreas Moeller
## CrossPoint v2.93 ##



Thu, 28 Nov 1996 01:17:00 GMT
 Integrating Paradox with a C++ executable

Quote:
> Your original statement said that ObjectPAL is an
> interpreted language. This is not true and thus my reply.

When you guys say Objectpal is compiled and not interpreted,
do you really mean that the Objectpal program is converted
into a sequence of real Intel machine instructions? The main
reason I ask: We just ordered Paradox Engine (yes I have
heard a little about the upcoming Borland Database Engine)
hoping and expecting that the multi-hour-long table
reformatting operations we have now written in Objectpal
will execute an order of magnatude faster using the Engine.

Christopher Schmidt
Tucson, Arizona, USA



Mon, 02 Dec 1996 20:26:00 GMT
 Integrating Paradox with a C++ executable
Paradox objects (Forms, Reports, Scripts, Libraries - anything that you can
design that gets saved with an L as the last character of the extension) are
compiled to a windows .DLL, but with a different extension.  A delivered object
is still a .DLL, but with access to the designer disabled.  Now whether this
fits your definition of "compiled to Intel machine code" is something I don't
know about, but Borland says that ObjectPal is not interpreted line-by-line
at run time (which as far as I know is the definition of an interpreted lan-
guage).
+==========================================================+
|     /\  ~~                   Ernie DeVries               |
| ~~ /  \/\      End User Computing & Information Services |

|   Northern Arizona University   "The Mountain Campus"    |
+==========================================================+


Tue, 03 Dec 1996 06:08:31 GMT
 Integrating Paradox with a C++ executable

 > When you guys say Objectpal is compiled and not interpreted,
 > do you really mean that the Objectpal program is converted
 > into a sequence of real Intel machine instructions?

Personally, that is my definition of compiled (on an Intel machine
leastways), and also my understanding of what ObjectPAL does.

 > The main
 > reason I ask: We just ordered Paradox Engine (yes I have
 > heard a little about the upcoming Borland Database Engine)
 > hoping and expecting that the multi-hour-long table
 > reformatting operations we have now written in Objectpal
 > will execute an order of magnatude faster using the Engine.

They could well run a lot faster, as OPAL table operations probably involve
a lot of overhead related to the object model, UI etc. which the engine
would freely ignore. Nothing to do with any distinction in the genetics of
the code produced, merely its environment (there's a metaphor in here
somewhere, desparately struggling to get out...)

cheers,
peter

==============================================================================
             Peter Hyde, South Pacific Information Services Ltd
             Christchurch, New Zealand -- Only a satellite away



Fri, 06 Dec 1996 08:24:28 GMT
 
 [ 15 post ] 

 Relevant Pages 

1. How to integrate an executable?

2. C++ executable called - foxpro 2.6 - Windows NT

3. VB4Pro DAO and C++ Builder 4 ... Integrating

4. Integrating C++ and SQL for Informix databases

5. Integrating c++ .dll's : Non-C'er needs help

6. Paradox 7 Can I make Executable Files

7. Paradox 7 Can I make Executable Files?

8. How can i make Paradox 5 databases executable?

9. How to make Paradox 6.0 databases executable

10. Making Paradox Forms/Tables into stand-alone executables

11. paradox files into executable files

12. executables with Paradox 6?


 
Powered by phpBB® Forum Software