Hidding or record

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In 2003, is there a way to hide or lock a specific record in a form display.
The record contains system information and I do not want it shown. I cannot
filter it out this record in the query because the record must be able to
store changing data. Filtering it out with criteria in the query seems to
void this function. So, is it possible to hide it on the form level?

Thanx, paul
 
Paul,

What is the process by which you want to "store changing data" into this
inaccessible record? If you are not entering/editing data in this
record via the form, then it would suggest the data is being modified
programmatically. And if this is the case, it shouldn't matter whether
you can see it on the form or not. Can you please give more details,
with examples?
 
The query on which this form is based, if also updated by another form. That
information gets dumped into a particular record and not into the records
generally. I never want this particular record changed by the user but it is
changed programmatically. I just don't want it to appear in the form as
part of the record set.

I am not clear about what you mean by an example. What's going on is that
the main form has a look-up section so that a booking agent can check for
black-out dates during the booking process. These black-out dates need to be
sequenced by date with the bookings to create a chronological and consitently
formatted pop-up reference. All of that works. However, the one fake record
that holds the black-out dates (as opposed to real records with bookings)
comes up in the form used to make the bookigs. I want to keep it off the
screen.

thanx, paul
 
Paul,

A am sorry, I should have mentioned at the outset that as far as I know,
there is no way to exclude one of the records from a form's record
source. So I was trying to find out what you are doing, so I could
suggest an alternative approach. I now understand why you want to
exclude the record from being shown on the form. What I don't
understand is why that record needs to be included in the form's record
source in the first place. Can't you do your programmatic changes to it
anyway... programmatic updates to data do not normally rely on that data
being included in a form's record source? Can't you refer to the data
from the point of view of the blackout dates for the form's purpose,
without it being part of the form's record source? What I meant by
"example" was something like this:
"Relevant fields in the query are BooBoo and BaaBaa and they typically
contain data such as "fred" and "wilma". The SQL view of the query is
like this...
SELECT Yaya, Tada from TheTable etc
This data is updated on the After Update event of the GooGoo control on
the GaaGaa form, using the following code...
Dim This
If Black Then
Do That
End If
.... and this is important for the purposes of the booking agent's usage
of the form because... etc"
 
Thank you for the time and consideration. I must agree that the design
structure is at fault. Your questions made me realize I must fix this on a
basic design level, rather than try patching a bad structure.

thanx, paul
 
Back
Top