Jeff,
The difficulty, as with so many of these things, is legacy. As you start to apply 'real' security to the system, so existing applications that have - let's say adapted to take advantage of the open security - will fail. It is the same problem that prevents the majority of applications from adding transaction management with well defined boundaries to their code.
Having said that, an SQL table for example is unlikely to form part of a legacy application (or the legacy part of an application anyway) so these should be fully secured. It really should not be possible to write "sdfdsfs" into an integer column using the editor, as you can with UniVerse today.
Brian
________________________________________________________________________ This email was checked on leaving Microgen for viruses, similar malicious code and inappropriate content by MessageLabs SkyScan.
DISCLAIMER
This email and any attachments are confidential and may also be privileged.
If you are not the named recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information.
In the event of any technical difficulty with this email, please contact the sender or [EMAIL PROTECTED]
Microgen Information Management Solutions http://www.microgen.co.uk ------- u2-users mailing list [EMAIL PROTECTED] http://www.u2ug.org/listinfo/u2-users
