[quoted text, click to view] Jon Slaughter wrote:
> "Jonathan Roberts" <gremln007@diynics.com> wrote in message
> news:BW2Eh.60462$5F3.19331@newsfe14.lga...
>> Jon Slaughter wrote:
>>> "Ed Murphy" <emurphy42@socal.rr.com> wrote in message
>>> news:45dfcda2$0$28111$4c368faf@roadrunner.com...
>>>> Jon Slaughter wrote:
>>>>
>>>>> No asp and no SQL. It uses php and mysql but I have sqlexpress that I'm
>>>>> using to test with.
>>>> Why the heck wouldn't you use MySQL for testing as well?
>>> Did I ever say I wouldn't???
>> This thread confuses me... Why aren't you simply connecting to your
>> database (whatever it is) through ODBC from your application? This method
>> you're trying seems very odd unless I have missed some critical constraint
>> of your environment.
>>
>
> Connecting to the database using any client side scripting is only a
> security disaster. I have to keep the users as far away from the database as
> possible. If they are connecting to the database directly then they could
> potentially hack the server.
Adding extra levels is more likely to screw things up than add any
useful protection. You should simply restrict access at the database
server level. For instance, if a user should be able to update some
records in a table but not others, then you don't give them direct
access to the table (relying on the client software to behave) - you
only give them access to a stored procedure (or whatever equivalent
MySQL offers) that rejects any attempt to perform an unauthorized