RE: MI MBX vs MBO

[Doug]

Chris MBO is the 'object' file for later linking in a project.  It means that you have a sub or something which is not dealt with in the program.  Take the following example:   Declare sub main declare sub fred   sub main     print "Hello"     call fred end sub   The compiling of the above would generate an MBO file.   However if you actually put the code for FRED in the program like thus:   Declare sub main Declare sub fred   sub main     print "Hello"     call fred end sub sub fred end sub Then that would create an MBX - executable. The reason you get the MBO is because the compiler thinks that 'SUB FRED' is dealt with by another file which is listed in a project file.  A project, or MBP file would look like this:   [LINK]  Application=myprogramname.mbx  Module=a_compiled_MB_that_contains_some_code(subs_etc).mbo  Module=another_compiled_MB_that_contains_some_code(subs_etc).mbo   That way your programming work can be better structured for easier maintaining/debugging.   Hope that helps! Regards   Doug       -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of galmala Sent: 09 September 2000 01:51 To: [EMAIL PROTECTED] Subject: MI MBX vs MBO Hey guys,   Just a quick question concerning MapBasic. I am writting several small programs at the moment. When I attempt to compile these files, they sometimes are compiled as an MBX file, and other times they are compiled as an MBO file! Any suggestions as to why this is the case.   Thanks in advance,   Chris