Hi Lars,

I have had this happen to me once or twice before and usually it is because
I had declared a global variable with the same name and a different type in
two different modules. 

Did you change any variables recently?

I don't think it is a file size problem as I have had MBX compiling in the
300K region.

Regards

Martin


-----Original Message-----
From: Lars V. Nielsen (HVM) [mailto:[EMAIL PROTECTED] 
Sent: 27 August 2004 12:25
To: MapInfo-L
Cc: [EMAIL PROTECTED]
Subject: MI-L Size limit when linking an MBX ??

I'm building a rather large MapBasic utility for specialized database
administration, and suddenly MapBasic refuses to link my program. It will
however compile all my modules.

The error messages are the infamous:

    The instruction at "0x123456789" referenced memory at "0x987654321". The
memory could not be "written"
    The instruction at "0x123456789" referenced memory at "0x987654321". The
memory could not be "read"

I'm wondering whether it's a size limit issue somewhere in MapBasic. If I
replace one of the (large) modules with a dummy, it links my app without a
problem.

The (6) MBO's that go into the MBX are a total of 232 KB in size. Not much
by any standard, I would say, but somehow it makes MB barf.

Has anyone experienced something similar ? And yes, I _have_ tried to reboot
my PC ;-)

Windows 2000 Server, MapBasic 6.5.   I've also tried to link with 4.1, and
7.5 : exact same result.

Best regards / Med venlig hilsen
Lars V. Nielsen
--------------------------------------------------------
Hvenegaard & Meklenborg
Rugaardsvej 55, DK-5000 Odense C
Denmark
http://www.hvm.dk


---------------------------------------------------------------------
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Message number: 13113






---------------------------------------------------------------------
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Message number: 13115

Reply via email to