Knowing the general reason for getting a MBO and not a MBX is well described
in Ben Crane's answer. Locating the guilty part is something else. I have
imagined a simple way and I would appreciate, and I am sure many other
mi-listers also, to know if it can be improved. It involves creating a
project with a single module, the GUILTY_MBO, and linking it. The linking
process will generate errors that can be viewed in the project window and
will certainly identify the calls that are not "satisfied".
The project file is named "DETECT.MBP"
It reads
[LINK]
Application=DETECT.MBX
Module=GUILTY_MBO.MBO
Jacques Paris
e-mail [EMAIL PROTECTED]
MapBasic-MapInfo support http://www.paris-pc-gis.com
-----Original Message-----
From: Hiltbrunner, Daniel [mailto:[EMAIL PROTECTED]]
Sent: June 13, 2002 03:30
To: '[EMAIL PROTECTED]'
Subject: MI-L MI_L MB MapBasic doesn't produce MBX file, though no errors
are reported
Hi all
Can anybody explain while a certain MapBasic 5 program, which compiled fine
up to now, suddenly doesn't produce an executable anymore? It compiles fine
(no error reported), but only an *.mbo file is created, no *.mbx. The file
is rather big (including several functions etc.), so I won't post the source
code here. I tested it also on other systems, same result; other MapBasic
programs compile fine, so I suspect that there is still an error in the
source, but MapBasci doesn't report it. Any hints?
Thanks & best regards
Daniel Hiltbrunner
GIS Specialist
TDC Switzerland AG
---------------------------------------------------------------------
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
