Just recently, we've been to experience Access Violations with midas.dll
The message is in the form of:
Access violation at address xxxxxxx in module 'MIDAS.DLL'. Read of address
xxxx
Does anyone know what may be causing this, or how can I fix it?
Thanks
Adam
Adam H. <ah...@nospam.netconnect.com.au> wrote in message
news:399b63f7_2@dnews...
> Just recently, we've been to experience Access Violations with midas.dll
As to your P.S., I won't be in Australia this year.
--
Dan Miser
www.distribucon.com
Adam H. <ah...@nospam.netconnect.com.au> wrote in message
news:399c70cb_2@dnews...
> It's an unusual one. It doesn't happen all the time, but it is frequent. I
> haven't traced it down to a single call or function at this stage, however
> it seems to happens when we go to retrieve the next packet from the
server.
>
> Would this point to a bug in the midas.dll, or more so a problem with my
> script?
> BTW - Are you planning on going to the Sydney Borland Conference this
> Summer?
Hi Dan,
It's an unusual one. It doesn't happen all the time, but it is frequent. I
haven't traced it down to a single call or function at this stage, however
it seems to happens when we go to retrieve the next packet from the server.
I've just recently traded in for a new notebook, and put a new installation
of Delphi 5 on it. I forgot to run the update to 5.01, and I thought that
this may have been the problem. However, since then, I've ran the update,
and re-built the project, but still with these error messages.
Would this point to a bug in the midas.dll, or more so a problem with my
script?
Thanks for your help...
Adam
Thanks for your reply. I'll try and chase it down a little more...
Regards
Adam
"Dan Miser (TeamB)" <dmi...@execpc.com> wrote in message
news:399c8e27$1_1@dnews...
This is a two tier database application where ClientDataSet and
DataSetProvider are dropped onto a datamodule.
I am using the DataSetField to create the master detail relationship in my
application.
This problem occurred after I modified master data and perform Master
CDS.ApplyUpdates(0). I traced the code and found out it occurred in the
DataSetProvider's BeforeUpdateRecord Event (Master) after it hit the Raise
Exception.Create('xxxxxx'). However, it will work fine if the program does
not execute the Raise Exception statement. Also, this does not happen in
the detail table.
Pls help.
Thanks in advance.
Raymond Ching
Adam
"Teik Lim Ching" <tlc...@pc.jaring.my> wrote in message
news:8noccl$pa...@bornews.borland.com...
Neither try..except nor try..finally statement in between the applyupdates.
Thanks
Raymond Ching
Adam H. <ah...@nospam.netconnect.com.au> wrote in message
news:39a0632f_1@dnews...
It's got me beat. I know I can have AV's if I have try / except statements
that include
the applyupdates command.
Maybe your problem is similar to mine - but I haven't figured mine out
yet... :-(
Adam
"Teik Lim Ching" <tlc...@pc.jaring.my> wrote in message
news:8nq667$gm...@bornews.borland.com...
I have tried to include the try..except statement in between the
applyupdates, I do get the same problem.
Thanks
Raymond Ching
Adam H. <ah...@nospam.netconnect.com.au> wrote in message
news:39a0d914_1@dnews...
Teik Lim Ching <tlc...@pc.jaring.my> wrote in message
news:8nvlj3$50...@bornews.borland.com...
In addition to this Access Violation error in Midas, is their any kind of
debuggin tool we could use to help you / borland track down the
problem within the MIDAS.DLL.
Does the address it gives (ie, Access violation at address xxxxxx) help
at all?
I still can't track down exactily what to do to cause the error. It occurs
when I use the GetNextPacket procedure, but not every time. I can't
see what conditions it occurs on, but I really need to get this fixed.
Thanks & Regards
Adam
Of course, full of doubt and worry when the problem will hit back again.
Attached with part of the code for your checking.
Thanks
Raymond Ching
begin 666 CdsError.txt
<encoded_portion_removed>
Teik Lim Ching <tlc...@pc.jaring.my> wrote in message
news:8p58k7$m...@bornews.borland.com...
> Again, sometimes I will get AV when execute the raise exception
statement.
> Any more feedback or suggestion on this issue ?