🚀 go-pugleaf

I don't know why you can't make your console work.  A GUI program is
allowed to open one console.  Might LabView have one open?

In any case, I think your approach is more difficult than it need be.
Create a simple console app which also creates a window.  Hide the
window or just don't make it visible.
Use the window to communicate with your DLL with one to a bunch of
bytes at a time via the WM_COPYDATA message or one byte at a time by
using a custom message (RegisterWindowMessage).  You can use some
oddball words for the window caption to make it easy to find
(FindWindow).  If you want to communicate back from the console to the
DLL then have the DLL also create a hidden window.

Is LabView the same as it used to be?  At one time the joke was that
you could tell a programmer who worked with LabView by the bottles of
aspirin and antacids he brought with him. <g>

.  Ed

> p Anders wrote in message
> news:405f5103$1@newsgroups.borland.com...
> Can anyone tell me if this can be done?
>
> The basic idea is that I have an application created in
> LabView (a 3rd party product) and I am trying to
> interface that with some communications software
> that is written in C++.  The C++ software has an
> "Application" class that writes messages to the console,
> essentially keep me informed as to the current program
> state.  I'd like to utilize this console window from within
> the DLL so I can see my program information that's going
> on inside the DLL.
>
> I have the DLL working but I can't get the console window to
> show up.  Does this have anything to do with not having a
> "main" that acts as the entry point to my application that
> creates a visible console?