 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
MC Ged Guest
|
Posted: Sun Jan 11, 2004 7:28 pm Post subject: Locate and EOF behavior |
|
|
I have been having a problem with LOCATE. I execute a TQuery on a DBASE
file with REQUESTLIVE = true. I loop over the rows until EOF is true. If I
now do a LOCATE, the application blows up completely. However, if I
open/close and then do a LOCATE, it does not blow up.
For what it's worth, if LOCAL
By the way, this whole business is happening on a stand-alone PC and it
happens in Win 98 and Win 2000.
Thank you for any insight you may have.
Marie Claire
|
|
| Back to top |
|
 |
Ignacio Vazquez Guest
|
Posted: Sun Jan 11, 2004 7:42 pm Post subject: Re: Locate and EOF behavior |
|
|
MC Ged wrote:
| Quote: | I have been having a problem with LOCATE. I execute a TQuery on a
DBASE file with REQUESTLIVE = true. I loop over the rows until EOF
is true. If I now do a LOCATE, the application blows up completely.
However, if I open/close and then do a LOCATE, it does not blow up.
|
How about if you do a .First?
| Quote: | For what it's worth, if LOCAL
|
....
You were saying?
--
Cheers,
Ignacio
|
|
| Back to top |
|
 |
Bill Todd (TeamB) Guest
|
Posted: Sun Jan 11, 2004 8:13 pm Post subject: Re: Locate and EOF behavior |
|
|
On Sun, 11 Jan 2004 14:28:34 -0500, "MC Ged" <mcged (AT) compuserve (DOT) com>
wrote:
| Quote: | I have been having a problem with LOCATE. I execute a TQuery on a DBASE
file with REQUESTLIVE = true. I loop over the rows until EOF is true. If I
now do a LOCATE, the application blows up completely. However, if I
|
Define "blows up completely". Is there an error message? If so, what
is it? You will find that the quality of the help you get on these
newsgroups varies directly with the amount of detailed information you
provide. :)
| Quote: | open/close and then do a LOCATE, it does not blow up.
|
How can you do a Locate on a closed dataset?
| Quote: |
For what it's worth, if LOCAL
|
The sentence above appears to be incomplete. Is something misssing?
--
Bill (TeamB)
(TeamB cannot respond to questions received via email)
|
|
| Back to top |
|
 |
MC Ged Guest
|
Posted: Sun Jan 11, 2004 8:13 pm Post subject: Re: Locate and EOF behavior |
|
|
..First causes the app to blow up as well.
"Ignacio Vazquez" <ivazquezATorioncommunications.com> wrote
| Quote: | MC Ged wrote:
I have been having a problem with LOCATE. I execute a TQuery on a
DBASE file with REQUESTLIVE = true. I loop over the rows until EOF
is true. If I now do a LOCATE, the application blows up completely.
However, if I open/close and then do a LOCATE, it does not blow up.
How about if you do a .First?
For what it's worth, if LOCAL
...
You were saying?
--
Cheers,
Ignacio
|
|
|
| Back to top |
|
 |
MC Ged Guest
|
Posted: Sun Jan 11, 2004 8:28 pm Post subject: Re: Locate and EOF behavior |
|
|
If I run the app from the IDE, I get the following error message:
This program has performed an illegal operation and will be shut down.
If the problem persists, contact the program vendor.
MYAPP caused an invalid page fault in
module IDDBAS32.DLL at 017f:4de3b711.
Registers: (blah blah )
Outside the IDE, I get:
This program has performed an illegal operation and will be shut down.
If the problem persists, contact the program vendor.
MYAPP caused an invalid page fault in
module KERNEL32.DLL at 017f:bff87ee0.
Registers: (blah blah )
In either case, the app shuts down.
As for the other 2 items you point out, I obviously need something stronger
than spell checker. I should have written:
1 - However, if I close/open and then do a LOCATE, it does not blow up.
2 - For what it's worth, if LOCAL SHARE = false, the app does not blow up,
but LOCATE doesn't always find what it should. Presumably, that's because
it's only looking in whatever is left in the cache.
Thanks,
Marie Claire
"Bill Todd (TeamB)" <no (AT) no (DOT) com> wrote
| Quote: | On Sun, 11 Jan 2004 14:28:34 -0500, "MC Ged"
wrote:
I have been having a problem with LOCATE. I execute a TQuery on a DBASE
file with REQUESTLIVE = true. I loop over the rows until EOF is true.
If I
now do a LOCATE, the application blows up completely. However, if I
Define "blows up completely". Is there an error message? If so, what
is it? You will find that the quality of the help you get on these
newsgroups varies directly with the amount of detailed information you
provide. :)
open/close and then do a LOCATE, it does not blow up.
How can you do a Locate on a closed dataset?
For what it's worth, if LOCAL
The sentence above appears to be incomplete. Is something misssing?
--
Bill (TeamB)
(TeamB cannot respond to questions received via email)
|
|
|
| Back to top |
|
 |
Bill Todd (TeamB) Guest
|
Posted: Sun Jan 11, 2004 10:11 pm Post subject: Re: Locate and EOF behavior |
|
|
You will have to use one of the work arounds that you have found.
Since the BDE is no longer being developed the problem will never be
fixed. If you are not using the latest version of the BDE (5.2) you
could try that and see if the behavior is any different.
--
Bill (TeamB)
(TeamB cannot respond to questions received via email)
|
|
| Back to top |
|
 |
MC Ged Guest
|
Posted: Mon Jan 12, 2004 2:36 pm Post subject: Re: Locate and EOF behavior |
|
|
Unfortunately I am using BDE 5.2. What a bummer...
Thanks,
Marie Claire
"Bill Todd (TeamB)" <no (AT) no (DOT) com> wrote
| Quote: | You will have to use one of the work arounds that you have found.
Since the BDE is no longer being developed the problem will never be
fixed. If you are not using the latest version of the BDE (5.2) you
could try that and see if the behavior is any different.
--
Bill (TeamB)
(TeamB cannot respond to questions received via email)
|
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|