Can we Flag Field in access table

[bunty20002001]

I have a Table with following Fields :
ID, PROFILE, ACCT_NUM

Each PROFILE can have Multiple ACCT_NUM and ACCT_NUM values can repeat itself across different PROFILE. ID column has unique values and is primary key.

ID PROFILE ACCT_NUM
1 LatePayment 11111111
2 LatePayment 22222222
3 LatePayment 33333333
4 OverLimit 11111111

I have designed the form such thatThe user can select any profile in form and randomly pull 2 Account Numbers.
After this I store this in a separate table and do further processing like creating report Etc.
Then again they move to a different profile and randomly pull 2 Account Numbers. I have coded correctly so far, but the business requirement is that once an Account Number has been selected, it should not be pulled again, even with a different Profile Name.
Is there a Flag that we can use associated with the ACCT_NUM field that has already been part of initial query, so that it is not part of further query selection?

Thanks!

[PianoMan64]

I have a Table with following Fields :
ID, PROFILE, ACCT_NUM

Each PROFILE can have Multiple ACCT_NUM and ACCT_NUM values can repeat itself across different PROFILE. ID column has unique values and is primary key.

ID PROFILE ACCT_NUM
1 LatePayment 11111111
2 LatePayment 22222222
3 LatePayment 33333333
4 OverLimit 11111111

I have designed the form such thatThe user can select any profile in form and randomly pull 2 Account Numbers.
After this I store this in a separate table and do further processing like creating report Etc.
Then again they move to a different profile and randomly pull 2 Account Numbers. I have coded correctly so far, but the business requirement is that once an Account Number has been selected, it should not be pulled again, even with a different Profile Name.
Is there a Flag that we can use associated with the ACCT_NUM field that has already been part of initial query, so that it is not part of further query selection?

Thanks!

Now the question that I have for you is that the Acct_Num, can it be pulled again after it has been processed?

If so, you're going to have to create some business rules in Code so that it's can't add the account number again, if whatever conditions that you're speaking of are true.

The way that I would do it, is simply create a Yes/No True/False Field in the PROFILE Table, and you create a group by query that will sort by the ACCT_NUM and the InProcess field that you will add.

If it returns True on the last Field displayed, then someone is processing it, if it returns false, then you can add that record for processing and check that particular profile item as in process.

Does that make sense?

Let me know.

Joe P.