Hi Tim,

> <<I hope you had a great weekend! >>
>
> I pulled my groin at hockey Sunday morning, so apart from a little trouble
> walking, I'm fine.

Hmm... it seems as though hockey's not agreeing with you entirely. (Or maybe
it's the opposing team). Maybe you guys should start taking up some real
sport, like Aussie football, or cricket! <vbg>

> <<I'll make this change, and let you know the progress. >>
>
> Cool, thanks.  That will at least rule out the possibility that there's
> something executing when we don't want it to be executing.

No problems. I'll keep you posted! Have a great day!

Cheers

Adam.

Adam,

<< Hmm... it seems as though hockey's not agreeing with you entirely. (Or
maybe it's the opposing team). Maybe you guys should start taking up some
real sport, like Aussie football, or cricket! <vbg> >>

I'll stick with hockey - at least we wear some decent padding, unlike you
Aussie football crazies.

--
Tim Young
Elevate Software
www.elevatesoft.com

Good Morning Tim,

Just letting you know we may have found the problem that was causing this
error!

I have found a rare bug within my application on certain queries where a
component referred to within the OnQueryProgress event may not exist,
causing an access violation.

Strangly though, it appears as thoughthis raised the above exception when
dealing in C/S situations.

Due to the nature of this bug, I was not able to reproduce it on demand, but
was able to remove the offending code (ensuring that the component existed
before calling the script), and since we have not seen this error, so I'm
hopeful (fingers crossed) that this problem has been fixed.

I just wanted to let you know, incase it helps in the future...

Best Regards

Adam.

Good Morning Tim,

Just letting you know we may have found the problem that was causing this
error!

I have found a rare bug within my application on certain queries where a
component referred to within the OnQueryProgress event may not exist,
causing an access violation.

Strangly though, it appears as thoughthis raised the above exception when
dealing in C/S situations.

Due to the nature of this bug, I was not able to reproduce it on demand, but
was able to remove the offending code (ensuring that the component existed
before calling the script), and since we have not seen this error, so I'm
hopeful (fingers crossed) that this problem has been fixed.

I just wanted to let you know, incase it helps in the future...

Best Regards

Adam.

"Adam H." <ahairsub4@pleaseREMOVEme.jvxp.com> wrote in message
news:05F133C9-CB8C-419E-B174-D93B5C0454A1@news.elevatesoft.com...
>
> Just letting you know we may have found the problem that was causing this
> error!
>

Thank goodness for that I can take the sandbags from around my server now.
I was watching this thread with great interest the blobs did it I'am working
on
a website Dbisam driven blobs galore.
It was just some left over code I think Tim's going to love you
gday mate
Rita

Adam,

<< Just letting you know we may have found the problem that was causing this
error!

I have found a rare bug within my application on certain queries where a
component referred to within the OnQueryProgress event may not exist,
causing an access violation.

Strangly though, it appears as thoughthis raised the above exception when
dealing in C/S situations. >>

Yes, what might happen is that the server-side may not get a proper response
back from the query progress callback, thus causing this type of error.
However, I will see if I can make the server handle this a bit more
gracefully.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Rita,

> Thank goodness for that I can take the sandbags from around my server now.
> I was watching this thread with great interest the blobs did it I'am
> working on a website Dbisam driven blobs galore.

Well, posting my findings on this news group was the big test! Normally I
find when I think I've fixed a problem, I wait a couple of weeks to see if
it raises it's head again. If it doesn't, I post the information.

Normally within 24hrs of saying "I've fixed it" publically, the problem
seems to magically re-raise, and I find I was wrong and it makes me look
like more of an idiot than usual.

So, keeping that in mind, I *really* should know in the next few hours if
the problem is truely fixed. <vbg>

> It was just some left over code I think Tim's going to love you

Either that, or hate me for all the stress I've caused!

> gday mate

Good day indeed! (If I don't get a call from my clients

Cheers

Adam.

Hi Tim,

> Yes, what might happen is that the server-side may not get a proper
> response back from the query progress callback, thus causing this type of
> error. However, I will see if I can make the server handle this a bit more
> gracefully.

Ahh - that makes sence. Either way - thank you so much for your ongoing help
with this issue (especially since it seems as though DBISam had nothing to
do with the problem at all - it was only the error message that was
confusing). I'm sorry to put you out so much, and even more sorrier for
doubting DBISam... what was I thinking!!! <vbg>

Cheers

Adam.

Adam,

<< Ahh - that makes sence. Either way - thank you so much for your ongoing
help with this issue (especially since it seems as though DBISam had nothing
to do with the problem at all - it was only the error message that was
confusing). I'm sorry to put you out so much, and even more sorrier for
doubting DBISam... what was I thinking!!! <vbg> >>

No problem at all - except for some typing and thinking, I didn't put forth
any effort at all.

--
Tim Young
Elevate Software
www.elevatesoft.com