I have ODE - A97 flavor and a complete set of the tools that came with it

[MLH]

Should mscomm32.ocx have accompanied the installation fileset?

[Rick Brandt]

MLH wrote:

Should mscomm32.ocx have accompanied the installation fileset?

Nope. The Readme file that should have been installed with the ODE lists
all of the included files and I don't see that one in the list.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[MLH]

>MLH wrote:

Should mscomm32.ocx have accompanied the installation fileset?

Nope. The Readme file that should have been installed with the ODE lists
all of the included files and I don't see that one in the list.

xxxxxxxxxxxxxxxxxxxxxxxxxx
Well, if it didn't come with it, that's probably a sure sign that I'm
not entitled to use or distribute it. What would I have to buy if I
really wanted to use it? I'm not sure that I do, but am curious
enough to ask.

[Rick Brandt]

MLH wrote:

MLH wrote:

Should mscomm32.ocx have accompanied the installation fileset?

Nope. The Readme file that should have been installed with the ODE
lists all of the included files and I don't see that one in the
list.

xxxxxxxxxxxxxxxxxxxxxxxxxx
Well, if it didn't come with it, that's probably a sure sign that I'm
not entitled to use or distribute it. What would I have to buy if I
really wanted to use it? I'm not sure that I do, but am curious
enough to ask.

What part of it do you think you want to use? AFAIK the only functionality that
can't be done with an API call is the TreeView.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[MLH]

Oh, I thought it had some serial-comm functionality
built in. Maybe not?

[Rick Brandt]

MLH wrote:

Oh, I thought it had some serial-comm functionality
built in. Maybe not?

Oh, I always confuse that one with the common dialog control. You're correct
that MSCOMM can ube used that way, but I have no idea if it can be distributed
or if so what is required to do so. It's possible that it just comes with
Windows and as long as you use late binding you can do what you want without
worrying about distributing it.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[MLH]

I'll probably forget about acquiring it or buying whatever s'ware
licenses its use. If I can manage to master the use of the
kernel32 & writefile and the related com port access tools,
I will go that route. Not having much success right now, so
there's another thread in which I'm soliciting input from the
gurus on that subject.

[Bri]

MLH wrote:

MLH wrote:

Should mscomm32.ocx have accompanied the installation fileset?

Nope. The Readme file that should have been installed with the ODE lists
all of the included files and I don't see that one in the list.

xxxxxxxxxxxxxxxxxxxxxxxxxx
Well, if it didn't come with it, that's probably a sure sign that I'm
not entitled to use or distribute it. What would I have to buy if I
really wanted to use it? I'm not sure that I do, but am curious
enough to ask.

It came with my copy of VB6. I use it in a POS app that needs to print
to a serial receipt printer. Its a pain that it didn't come with the
Access ODE and its a pain to install too. If I could have found another
way to communicate with the serial printer, I would have done that
instead. Its also a pain to have an extra VB app as an intermediary
between Access and the printer.

--
Bri

[MLH]

Ouch. That's not very encouraging. I mean, inability to communicate
w/ serial printer w/o that tool. I haven't used a serial printer in
a long time, so I haven't noticed that. But one would think that
there were serial printer drivers in windows that would handle the
need. I certainly would have expected so if I'd attached one to my
dev box. Totally sux. Thx for the 'heads up' on it. BTW (and not that
it matters) but what serial printer are you using?

It came with my copy of VB6. I use it in a POS app that needs to print
to a serial receipt printer. Its a pain that it didn't come with the
Access ODE and its a pain to install too. If I could have found another
way to communicate with the serial printer, I would have done that
instead. Its also a pain to have an extra VB app as an intermediary
between Access and the printer.

[Bri]

It is a Star SCP700 Receipt Printer. It does have Windows Printer
Drivers, but there were problems with them. They were PAINFULLY SLOW to
process and print as they converted all output to raster graphics (ie
didn't use any of the built in fonts in the printer). It was taking 5-10
seconds per inch of receipt. We decided to do straight DOS style send
ASCII characters straight to the Printer. Now a 10 inch receipt prints
in about a second (instead of over a minute). Sure they don't look as
pretty, but they don't have customers walking off without the receipt
because they can't wait for it.

The MSCOMM control was the only way I could find to send ASCII down the
COMM port directly. Perhaps someone out there has worked out an API
method that would eliminate the control, but I haven't been able to find it.

--
Bri

MLH wrote:

Ouch. That's not very encouraging. I mean, inability to communicate
w/ serial printer w/o that tool. I haven't used a serial printer in
a long time, so I haven't noticed that. But one would think that
there were serial printer drivers in windows that would handle the
need. I certainly would have expected so if I'd attached one to my
dev box. Totally sux. Thx for the 'heads up' on it. BTW (and not that
it matters) but what serial printer are you using?

It came with my copy of VB6. I use it in a POS app that needs to print
to a serial receipt printer. Its a pain that it didn't come with the
Access ODE and its a pain to install too. If I could have found another
way to communicate with the serial printer, I would have done that
instead. Its also a pain to have an extra VB app as an intermediary
between Access and the printer.