Check before viewable!!!!

[Stuart Millward]

This is the scenario....

I've produced [via the database wizard in fp2002] a set
of pages that alows me to add and edit entires to a
access database that are then deisplayed on my results
page {they are items for sale)

what i would like to do is......

add the function that users can add their own adverts but
the database entries would not be visable on the results
page until they had been vetted and agreed....POWER!!!!!

I'm sure this is easily sorted by you top developer boys,
but can a code hacker c+v merchant like me do it.....

stuart

 

[Stephen Travis]

The easiest way to do this is to add an 'approved' field that you can set via a separate form and then filter the displayed results
on this field...

WHERE (....) AND [Approved] = True

 

[Kevin Spencer]

Just to elaborate: The "approved" field should be given a default value of
false in the database, and the input form should not include the "approved"
field, so that the record will be inserted with the default value.

HTH,

Kevin Spencer
Microsoft FrontPage MVP
Internet Developer
http://www.takempis.com
Some things just happen.
Everything else occurs.

The easiest way to do this is to add an 'approved' field that you can set

via a separate form and then filter the displayed results

on this field...

WHERE (....) AND [Approved] = True

--

Stephen Travis,
Microsoft MVP - FrontPage

This is the scenario....

I've produced [via the database wizard in fp2002] a set
of pages that alows me to add and edit entires to a
access database that are then deisplayed on my results
page {they are items for sale)

what i would like to do is......

add the function that users can add their own adverts but
the database entries would not be visable on the results
page until they had been vetted and agreed....POWER!!!!!

I'm sure this is easily sorted by you top developer boys,
but can a code hacker c+v merchant like me do it.....

stuart