L
Louis Levine
I have an Access ADP. In order to search within it, I have 2 tables: One is
a table that holds all the relevant ClientIDs (zUser1) and the other is the
table with all the data (Clients). I've also created a view, vClients that
has all the fields that would ever be updated.
The recordsource for my form is set on load, and is always Select .... From
vClients INNER JOIN zUser1 on vClients.ClientID=zUser1.ClientID.
When I do a search, I clear out the zUser1 table, and repopulate it with the
new set of IDs. Then, I requery the form, which should work. The problem is
that it crashes after a few searches.
I was getting the same results (crash) when I was using a different method
for searching. Previously, I just updated the recordsource of the form with
the new search. But it was crashing there also.
It's never the same search that does it, it can happen right away, or take a
few searches to trigger the crash. But it's reasonably consistent.
This is happening with both Access XP and Access 2003. This is NOT happening
in Access 2000, which is what I developed it in.
Any help would be greatly appreciated. And I apologize for the cross-posting
on this.
-Louis Levine
a table that holds all the relevant ClientIDs (zUser1) and the other is the
table with all the data (Clients). I've also created a view, vClients that
has all the fields that would ever be updated.
The recordsource for my form is set on load, and is always Select .... From
vClients INNER JOIN zUser1 on vClients.ClientID=zUser1.ClientID.
When I do a search, I clear out the zUser1 table, and repopulate it with the
new set of IDs. Then, I requery the form, which should work. The problem is
that it crashes after a few searches.
I was getting the same results (crash) when I was using a different method
for searching. Previously, I just updated the recordsource of the form with
the new search. But it was crashing there also.
It's never the same search that does it, it can happen right away, or take a
few searches to trigger the crash. But it's reasonably consistent.
This is happening with both Access XP and Access 2003. This is NOT happening
in Access 2000, which is what I developed it in.
Any help would be greatly appreciated. And I apologize for the cross-posting
on this.
-Louis Levine