holding a record for later / holding table?

[imoree]

hello Everyone;

i am trying to figure out where to start with this or what am i missing.

i am attempting to :

• save primary ID & foreign Key fields
  
• along with an order ID on current table ( invoice table)
  

Sometimes i need to "HOLD" the record for later and everything i have seen shows me that i only need to create a list. TO me this makes no sense.

Or is it just me.

Eg. If i do a script design like this:

1. Save Current record [ commit ]
   
2. copy invoice ID into a new field ( held_records )
   
3. conditionally format a button that was grayed out to be either Green/ red & show text " UNHOLD " record(s)
   
4. If user chooses to "UNHOLD" records, they will
   
5. Go to [ recordID ] - that was in the held_records table
   

-i

[bcooney]

Why a separate table, and not a status on the Invoice?

[doughemi]

Why not create a Hold field (boolean) and set it to 1 or 0 as needed?

[comment]

It depends on what "hold" means: should it apply to all users or the current user only? If the latter, should a record be held for the current session only, or until it's explicitly released by some action of the user?

[imoree]

It has to be "Explicitly released by the user having to Press the UNHOLD button in order to "CONTINUE" the process.

It is specific to the invoice # & not the user..

-

[comment]

Well, then it's a field in the Invoices table - as suggested by the other responses.

[imoree]

great. will try that.. Simple enough . KISS method is just too hard to follow isnt it?