Glen
Tue Sep 16 16:31:34 CDT 2003
Same system. When I try to launch it thru its .exe file
the program just flashes. It works fine from the command
line do getfrommicr.
I tried changing the datasession within the main form when
i change from the default 1 to 2 the form acts the same
from calling the .exe file just flashes but when i run it
from the command line with datasession set to 2 it echo's
some values to its own screen.
thanks Rick
Glen
>-----Original Message-----
>Glen,
>Is this the same system, or a different one? Be aware of
the SET settings that have different defaults in the two
environments, make sure you explicitly set them in the
application to be the same. By especially mindful of the
whole group of SETs that get reset in each Private
Datasession. (Set the Help file topic "SET DATASESSION
Command" for a list.
>
>Rick
>
>"Glen Wagner" <mozillapost@hotmail.com> wrote in message
news:461c01c37c7e$1e734460$a501280a@phx.gbl...
>> Well 6.0.81.69 is the version I have which brings me
back
>> to "What would cause an application that reads the comm
>> port to work properly in a development environment but
>> return and error OLE IDispatch exception code 0 in a
run
>> time environment"? saying Comm port 1 is already open.
>> I am using a similar application to moniter the port
the
>> scale is on "4" and it causes no error.
>> Glen
>>
>> >-----Original Message-----
>> >Glen,
>> >The best source of MS version information is the DLL
>> Database -
http://support.microsoft.com/default.aspx?
>> scid=/servicedesks/fileversion/dllinfo.asp&SD=msdn
>> (yup .OCX's are actually .DLL's!)
>> >
>> >It shows the latest version as 6.0.81.69 and it came
>> with the VS/VB/VC++/VFP 6.0 releases.
>> >
>> >Rick
>> >
>> >"Glen Wagner" <mozillapost@hotmail.com> wrote in
message
>> news:3bcc01c37bfe$8af09c80$a501280a@phx.gbl...
>> >> Thanks for the Tip! Just to confirm yours worked
under
>> >> foxpro but no as a atand alone app? Thats the case
>> with
>> >> mine. Also do you know where I can download another
>> >> mscomm32.ocx or compare to the one I have from VFP6.
>> >> Glen
>> >> >-----Original Message-----
>> >> >I have had a similar problem caused by the version
of
>> >> mscomm32.ocx that was
>> >> >registered on my machine. As a matter of fact the
>> control
>> >> that is installed
>> >> >with VFP5 or 6 would not work, but if I installed
VB6
>> the
>> >> control worked. I
>> >> >now copy a known good mscomm32.ocx to the target
>> machine
>> >> and register it
>> >> >seperately and not allow the installer to register
it.
>> >> Also if the comm port
>> >> >is not avaliable a similar error will occur.
>> >> >
>> >> >jrg
>> >> >
>> >> >
>> >> >"Glen Wagner" <mozillapost@hotmail.com> wrote in
>> message
>> >> >news:057d01c37976$5becc010$a101280a@phx.gbl...
>> >> >> Hello
>> >> >> I am using a form with MSCOMM to comunicate with
A
>> MICR
>> >> >> Reader connected to it on com1. I have the com
port
>> set
>> >> >> on the ININ Event thru passed variables from the
>> calling
>> >> >> procedure. I then wait for input from the MICR
>> reader
>> >> and
>> >> >> simply write each line to a .dbf. The form works
>> fine
>> >> in
>> >> >> development under foxpro but when I compile the
>> project
>> >> i
>> >> >> consistantly get an error "OLE IDispatch
exception
>> code
>> >> 0"
>> >> >> from the forms "MICRREAD.CPORT.INIT" Procedure
which
>> >> >> contains
>> >> >> this.commport = micrcom && 1
>> >> >> this.settings = micrset && "9600,N,8,1"
>> >> >> THIS.PortOpen = .T.
>> >> >>
>> >> >> What would cause it not to run compiled as an exe
>> but to
>> >> >> run ok under foxpro?
>> >> >> Thanks
>> >> >> Glen
>> >> >>
>> >> >
>> >> >
>> >> >.
>> >> >
>> >.
>> >
>.
>