||Re: requery problem
||Wed, 08 Jan 2020 08:00:04 -0500
Hi Akshat.. I attached a picture of the error message in my last post.
Akshat Kapoor Wrote:
> On 08.01.2020 14:31, charlie wrote:
> > Here it is... Another thing is that when this happens after I click on a button that causes it, looks like the program is doing something for a second before the error message appears. The little windows circle appears for that second. Also it forces a null .dbf to appear in the directory. Named this or similar: _QSQL518.DBF.
> > Something similar happens in one other completely different form just after I push a button. That happens only on the second, third or fourth time you push the button like this. It never happens the first time you click, only on the second or more times. But even when successful, you get a hesitation like it is doing something for a second even if successful..
> > I have never looked into the other form error problem as I've been baffled on this. Would be great to figure it out.
> _qsql???.dbf files are temporary files created when a query is run. They
> should be deleted when the form closes but at times they are left behind.
> I would request you to close all dbase applications and then search for
> and delete all _qsql files which are there in the directory in which
> this file appears.
> It would be very helpful if you send us the screen shots of error. No
> need to send whole desktop app (if that contains sensitive info) just
> the msgbox that displays the error is sufficient. But we need the exact
> message of error.
> Without the exact message it will be a blind shot.
> > /
> > Akshat Kapoor Wrote:
> >> On 08.01.2020 04:25, charlie wrote:
> >>> OK the requery works well but it make the program unstable. After the first 1 or 2 times trying to use a push button which deletes items then requeries to change the grid and other entryfields inevitably the program says that it has an execution error or something like that then shuts down. It is absolutely caused by the requery which I have in ongotfocus.
> >> Requery() alone will never cause a problem. There is something else also
> >> involved. Will request you to paste a screenshot of the error message.
> >> Regards
> >> Akshat