Set recordset or use filter?

calvinle

Registered User.
Local time
Today, 00:37
Joined
Sep 26, 2014
Messages
332
Hi,

Each programmer has their own method of working with access. But I am more concern about performance and accuracy of data changes.

I have a form with a command button to open another form to view all cheques that was made to that member. There is no relationship between tables. Because thays how it was built before and I don't to start changing things, the risk of causing issue with the database which is currently working well except slow loading speed. Actually, the loading of cheque use a filter in that new form on load (set to continuous).

1/ is it safer to use that filter or should set a new recordset to that form on load? Im looking into speed and accuracy of data changes.

Thabks
 
My suggestion? Open a bound form (bound to the checks list) from the command button, but include a form filter to select based on member ID.

1. Faster than trying to do explicit recordset operations to populate a form because the new form's recordsource is treated as a query. Recordset manual operations have to be emulated so become problematic.

2. Far safer, because once you get the form right, it will be properly maintained by the Access form management routines when you save anything.

3. With bound recordsets, the form's recordset manipulation is automatic within Access itself so you don't have to "roll your own" navigation.
 
The form is already boundsd to a table, but then use filter to pull all cheques related to that member.
At the same intance, its multi uset envrionnement, another user can also perform the same thing on another member.
So we will have 2 user accessing the same table located in backend, but use different filter. Will that cause any problem?
 
If this is a split database and each user has his/her own front-end, they never see each other. You said they used the same backend, but not to worry. The way Access does its thing is that it builds a temporary list in the FE (we think) to hold a working list. In essence, every list is on a different FE / different machine and is therefore invisible to all users. They can only see what THEIR FE file does.

Using a form and filter will be tons faster than any other approach you could devise, so I'd say you are on the right track there.
 

Users who are viewing this thread

Back
Top Bottom