[Brief pause for a late lunch :-)]
> I'd love to know exactly what the problem was, so i could say, hey get
> this ***.dll and fix their problems that way. The code that generally
> gave the errors was when using DeviceCapabilities to find printer Info,
> maybe it was just bad print drivers (this of course would not be
> un-common)?
Borlandmm.dll is the one with the shared memory manager in it, which also
implements GetMem (details in the ShareMem unit). It's extremely unlikely
that the problem is a corrupt borlandmm.dll, so you can probably ignore my
comments there. :-) It's much more likely that it's a bad print driver or
similar, although it beats me why that would be fixed when you avoided calls
to GetMem. Something really subtle no doubt.
> Also, I didn't say that all my users had this problem, although I did
> say a lot of systems (oops), but on the machines that have had problems,
> and I spent ages trying to sort their problems out, it all came down to,
> if i removed the Getmem from the code it worked like a charm.
Still have the code lying around? Is it short enough to send to the list?
Cheers,
Carl
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
