Hmmm...so you never have undersecretaries named "James O'Brien"??

<grin/>

Good point. However, we have only ever had one O'something, and that was in a bound form, so no need to pass the values in a query string.

I am working more on this issue since it may well come up in the future. =)


mmcdonal

Look it up at: http://wrox.books24x7.com

BOUND FORM!

*THAT* is what I was thinking of, when I asked about "form fields used in queries".

So you have to pre-bind form fields in some way...to tables, presumably? So not as flexible as PHP. (Not that I'm enamored of PHP!)

It all makes sense now.

Yes, PHP has its own issues, too. See: http://www.securereality.com.au/studyinscarlet.txt for a good paper on PHP vulnerabilities.

Access has some built in string exploit protections. Like you can't do this for data entry: Smith'; DROP TABLE Employee;



mmcdonal

Look it up at: http://wrox.books24x7.com

Thanks guys, Placed your suggestions into practice and all is well. Much appreciated. I placed a new post on selecting a record and placing it onto a recordset to populate the form. Basically the reversal of what you helped me with... the syntax strikes again.

If you have a free minute come on over as I sure it will be loads of fun :-)

http://p2p.wrox.com/topic.asp?TOPIC_ID=75165


Sincerely,

Luis