unstable query

[Bibi]

I have a reservation database that I designed and have been using for 7 or so
years now. I had help designing the query I show below from a discussion
group several years ago. In the past it would, very rarely, erase
itself............It just wouldn't work and there would be no language in the
SQL view and I would have to paste in a copy. Recently it has become
completely unstable when I run it in Access 2003 on my home computer. I
open a good copy of the data base, run the query once an dit will work - the
second time I try to run it - it has erased itself......When I run it on my
office computer with Access 2000 it is fine. I've checked for viruses,
etc......Any ideas what the problem could be? I uninstalled and reinstalled
Access and it worked but only for a day.....Is there anything intrinsically
unstable about the following query? Do I have a virus? I use Norton.

SELECT *
FROM tblLeases
WHERE (((tblLeases.Arrive)=(SELECT Min([Self].[arrive])
FROM [tblLeases] AS [Self]
WHERE [Self].[Property] = [tblLeases].[Property]
AND [Self].[arrive] >[FORMS].[favailable].[Text1])));

 

[John W. Vinson]

I have a reservation database that I designed and have been using for 7 or so
years now. I had help designing the query I show below from a discussion
group several years ago. In the past it would, very rarely, erase
itself............It just wouldn't work and there would be no language in the
SQL view and I would have to paste in a copy. Recently it has become
completely unstable when I run it in Access 2003 on my home computer. I
open a good copy of the data base, run the query once an dit will work - the
second time I try to run it - it has erased itself......When I run it on my
office computer with Access 2000 it is fine. I've checked for viruses,
etc......Any ideas what the problem could be? I uninstalled and reinstalled
Access and it worked but only for a day.....Is there anything intrinsically
unstable about the following query? Do I have a virus? I use Norton.

SELECT *
FROM tblLeases
WHERE (((tblLeases.Arrive)=(SELECT Min([Self].[arrive])
FROM [tblLeases] AS [Self]
WHERE [Self].[Property] = [tblLeases].[Property]
AND [Self].[arrive] >[FORMS].[favailable].[Text1])));

There's nothing about a query that would cause it to commit suicide in this
way! I strongly suspect that your database is corrupt, possibly with some
problems in the hidden system tables.

Check out the suggestions at Tony Toews' corruption FAQ:
http://www.granite.ab.ca/access/corruptmdbs.htm

Start by backing up your database (you may need a copy if some of the possible
solutions do more harm than good).

 

[Jerry Whittle]

There were some bugs in early versions of Access 2003 but they have been
fixed and 2003 should be very stable. Open up Access and go to Help, About
Microsoft Access. The first line should have SP3 at the end of it. If not,
you are missing patches.

There's nothing in your query that should cause such behavior. As it works
correctly on one computer, but not the other, it's probably something wrong
with the computer in question.

I have had trouble uninstalling Office in the past. MS may have a tool which
can completely remove Office. Notice that I didn't just say Access, but
rather, the entire Office suite to fix problems.

In a couple of cases I wiped the hard drive clean and started completely
over with Windows, Office, and any other needed program. Often it's easier to
just buy a new PC.