One thing you could do is create a Bad_Word table, fill it with anything you don't
want to
allow in the data (bad words or phrases, html code, etc). Then test the text against
the
table:
<cfquery name="bwCheck" datasource="whatever">
select count(*)
from bad_word
where field_name like '%#form.text#%'
</cfquery>
<cfif bwCheck.RecordCount GT 0>
<cfset errors = "You have entered unacceptable text blah blah">
<cfelse>
(the text is acceptable - do your insert here)
</cfif>
Of course, using wildcard searches slows your processing time.
--------------------------------------------------
Brenda Gammon
[EMAIL PROTECTED]
TraderOnline.com
[EMAIL PROTECTED] wrote:
> Our organization may soon need to allow unknown persons to register as users
> and be allowed to input information into our systems. I don't have any
> worries about the technical aspects of this, but I wondering what policies &
> procedures, if any, other organizations use to keep bored or unfriendly
> people from entering offensive data. Some of the data that people would
> enter would be visible to other persons looking for information on our site,
> so we don't really want people identifying themselves as Hitler or writing
> that they work for the Klu Klux Klan.
>
> Any ideas?
>
> -------------------------------
> Martin Herbener
> [EMAIL PROTECTED]
> Kentucky Department of Education
>
> ------------------------------------------------------------------------------
> Archives: http://www.eGroups.com/list/cf-talk
> To Unsubscribe visit
>http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
>message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
