Now that has got me thinking in what the differences between the previous caching code and the crashing caching code are.
The code that rarely crashes will probably not include characters over ASCII 128, or is real or Longint arrays. I say probably because what was stored was the query parameters and I *believe* that I store the unconverted version. The data that was guarenteed to crash Active4D will be very likely to contain characters with accents, or other non printable low ASCII value characters. Since this was product names and descriptions in German. So probably items with >128 ASCII and possibly lower than ASCII 32 due to the source of this data. Michael Bond ----- Original Message ----- From: "Ishimoto Ken" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 10, 2002 9:48 PM Subject: Re: [Active4d-dev] get global with index > > I have tested the Lock/Unlock variables and that works fine, all of the > > writing to the globals are protected by the above, so I was going to > > get > > around to testing the reading. I believe it is related to the number of > > globals present, since removing this exact set of 5 array with 4000 > > elements causes things to be a lot better. The strange thing is that > > the > > code that we removed is almost identical to other caching code that I > > wrote, > > so I was very baffled. > > In my case it was only an Text array with about 40 elements. And not > every time > but mostly crashed. I think it is not the size of the array. Maybe what > is inside the > array. I had only tested it with Text arrays. in the text array was > japanese char, > and I thought maybe it didn`t like the double byte chars.... > > Ken Ishimoto > > > _______________________________________________ > Active4d-dev mailing list > [EMAIL PROTECTED] > http://aparajitaworld.com/mailman/listinfo/active4d-dev >
