Need help with creating a property

  • Thread starter Thread starter Lee
  • Start date Start date
L

Lee

Hi folks,

I have a report and a message (form) that both appear
when users click on a particular button. On this message
I've included a box to check where users don't want to
see the message again. For this to work I guess I need
to create a further property to assign a yes/no value to.
This is where I come unstuck because I don't really know
what I'm doing! I pinched some of the code in the
Northwind database that I thought was applicable but as
it was more relating to the Statup processes I couldn't
get it to work. As an interim measure I've created an
extra field in one of the tables for the purpose of
assigning a yes/no value but I know this is a naff way of
doing it as the value is assigned to every record in the
table - very naff indeed! Are you able to explain in
layman's terms how I can create a property and then use
it to prevent a form from appearing.

Many thanks for any help or advice you can give.

Lee

Thanks,

Lee
 
Thanks for such a quick response Dan.
I've done as you suggest Dan and that's fine. The only
trouble with using a Table though is that as the database
is used by a number of people, the value will apply to
all users whereas creating a property for a Form object
will mean that the 'front end' part of the database will
then be the arbiter of whether the message is displayed
or not, rather than the back-end.
If you can also give any advice on property creation I'd
be pleased to hear it!
Regards,

Lee
-----Original Message-----
Hi,
You have the right idea. Just create a table that holds the yes/no
value instead of using one of your existing ones.

--
HTH
Dan Artuso, Access MVP


"Lee" <[email protected]> wrote in
Click to expand...
message news:[email protected]...
 
OK, thanks for all your help Dan. As you say, I can keep
this particular table with the front-end - I hadn't
thought of doing that! derrr!

Regards,

Lee

-----Original Message-----
Hi Lee,
THing is, unless I am mistaken on this, you can't create a user defined
property for a form. You could use the tag property, but in order to make it
persistent, you would have to open the form in design view then save.

The simplest solution would be to have your table in the
Click to expand...
front end, then it would apply to
each user individually.
You could also use SaveSetting and GetSetting to write and read from the registry.
--
HTH
Dan Artuso, Access MVP


"Lee" <[email protected]> wrote in
Click to expand...
message news:[email protected]...
 
Back
Top