Re: Attention all "Barcleys" Bank Customers
- From: Derek Potter <derekatspothyphenonhyphensolutionsdotcodotuk@xxxxxxxxxxxxx>
- Date: Mon, 06 Feb 2006 08:59:37 +0000
On 6 Feb 2006 07:56:04 GMT, Marcus Houlden <spam@xxxxxxxxxxxxxx>
wrote:
On Sun, 05 Feb 2006 22:32:13 +0000, Prai Jei <pvstownsend@xxxxxxxxxxxxxxxxxxx>
wrote the following to uk.misc:
Never seen one of those. One of our applications, written in VB so compiled
with one of B**l G***s' own nasties, is fond of failing to start, getting
about halfway then putting up a message box along the lines of "The
instruction at <hex address> tried to access memory at <hex address>. The
memory could not be read" and dropping out when you press OK. After three
or four instances of this, and making no other changes, it then starts up
perfectly and runs OK indefinitely.
Isn't that just normal behaviour for anything written in VB, not to mention
the IDE itself?
I'm stuck in a time warp with VB5 and I can't say I've found any such
thing. Mind you my apps are always small. The only thing that does
screw it up is forcibly terminating execution in the IDE when it's
stuck in a loop and I've forgotten to put a DOEVENTS in it. It usually
needs a re-launch then. Same goes for those wretched modal input
boxes but the less said about them the better.
.
- References:
- Re: Attention all "Barcleys" Bank Customers
- From: Derek Potter
- Re: Attention all "Barcleys" Bank Customers
- From: Derek Potter
- Re: Attention all "Barcleys" Bank Customers
- From: Derek Potter
- Re: Attention all "Barcleys" Bank Customers
- From: Derek Potter
- Re: Attention all "Barcleys" Bank Customers
- From: Prai Jei
- Re: Attention all "Barcleys" Bank Customers
- From: Marcus Houlden
- Re: Attention all "Barcleys" Bank Customers
- Prev by Date: Re: Moderate geek. . .
- Next by Date: Re: Result!
- Previous by thread: Re: Attention all "Barcleys" Bank Customers
- Next by thread: Re: Attention all "Barcleys" Bank Customers
- Index(es):
Relevant Pages
|