RE: MI MapInfo 5.5 Crash

[Trey Pattillo]

Here's what I have found   1) be sure that you declare all queries INTO a named result > select * from table where a=b INTO TEMP 2) close TEMP as soon as you done with it 3) keep tables closed as much as you can...reopening slows down app but the time is worth it 4) use variables as much as possible including "object" -- really helps control memory usage   MOST of all if you using Win9x you were already in trouble ! ! It uses resources just link 3.x and can't decide if it's 16/32 bit or better put.... a 32 bit display of a 16 bit program built with a 8 bit compiler for a 4 bit processor by a 2 bit company that can't stand 1 bit of competition........   The 911 app that I wrote with Delphi 4 runs 24/7, reading the phone/address [like caller id], looks it up, creates "pushpins" at the location, allows a far superior user query for failures or general purpose lookups, has 10 additional tables [subdivision, water, etc] and has no problems.  Of course it runs on NT4w SP5 with 64meg on a P-200mmx using MI4.1.  I have noticed that after 1500 to 2000 hrs [about 2.5-3 months NT gets a bit tired, no matter what your doing, including my "crash & burn" development cycles -- reboot time].  Yesterday I was at a location that is still using the old PowerBuilder/Paradox database app [the version of PB is a 16 bit app] and it had gone blind, lost all it "edit boxes" and labels but the window was still there, after about 800 hrs [back to the "resource" issue].     Hope this helps.................   Trey Pattillo [EMAIL PROTECTED] http://www.wap3.com