PaddyIrishMan
Registered User.
- Local time
- Today, 13:35
- Joined
- Jun 5, 2002
- Messages
- 166
Hi,
I have a split B/e F/e Database. The B/e resides on a Server & each Client has an MDE file.
Also involved is a linked Database which I use as a resource for shared company-wide data. The B/e database has linked tables from this Database.
So in the MDE file there are Forms, Queries that use the B/e Database tables & Queries that use the Linked tables.
Recently, all of the Queries that use the Linked tables went a bit mad.... they started returning all information
from the tables that they were running from regardless of criteria.
When the queries were opened in design view, they were fine.
When I compacted both database the issue still occurred.
Only when I compacted the MDE file(s) did the problem stop happening.
As far as I am aware we had no significant network troubles or power outages that I can use as a factor
in the events leading to the error.
I have no idea how this has happened - the only solution I can think of is to include a button to compact/repair the mde file in my next release.
Has anybody had similar problems?
Any ideas why this happened?
Thanks,
Patrick
I have a split B/e F/e Database. The B/e resides on a Server & each Client has an MDE file.
Also involved is a linked Database which I use as a resource for shared company-wide data. The B/e database has linked tables from this Database.
So in the MDE file there are Forms, Queries that use the B/e Database tables & Queries that use the Linked tables.
Recently, all of the Queries that use the Linked tables went a bit mad.... they started returning all information
from the tables that they were running from regardless of criteria.
When the queries were opened in design view, they were fine.
When I compacted both database the issue still occurred.
Only when I compacted the MDE file(s) did the problem stop happening.
As far as I am aware we had no significant network troubles or power outages that I can use as a factor
in the events leading to the error.
I have no idea how this has happened - the only solution I can think of is to include a button to compact/repair the mde file in my next release.
Has anybody had similar problems?
Any ideas why this happened?
Thanks,
Patrick