Stephen,
A very common reason for this is that you probably have written code that
refers to a sub that is declared but not actually present. As an example,
the following:
Declare Sub MAIN
Declare Sub DUH
Sub MAIN
Call DUH
End Sub
---will compile as an MBO. DUH is declared, but not written.
On the other hand---
Declare Sub MAIN
Sub MAIN
Call DUH
End Sub
---will report errors when compiling. DUH is called, but not declared.
But the following---
Declare Sub MAIN
Declare Sub DUH
Sub MAIN
Call DUH
End Sub
Sub DUH
End Sub
----will compile as a MBX, even though there's actually nothing in DUH. I
hope all this helps. Good luck.
Mike Jenne
JCSI
At 11:54 PM 3/10/00 -0500, Stephen R. Riese wrote:
>Greetings,
>And just when I thought I was getting the hang of MB/MI. When I compile my
>code, MB now compiles it as a .MBO file. I don't know why it does that --
>it was compiling fine (i.e., .MBX) before. Then, all of a sudden, it
>starts compiling as .MBO. And, of course .MBO files don't run by
>themselves in MI. Is there something I entered in the code that makes do
>this? I've tried Save As, renaming the file, cutting and pasting into a
>new file, but it always comes out as .MBO. My other files still compile as
>.MBX. The help files and users manuals (both MI and MB, version 5.0) aren't
>helpful.
>Please help me get the .MBX files back.
>Thanks,
>Steve Riese
>
>[EMAIL PROTECTED]
>----------------------------------------------------------------------
>To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
>"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
>
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
