mery Scott NCC-1701
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-u2-
> [EMAIL PROTECTED] On Behalf Of Ray Wurlod
> Sent: Friday, June 10, 2005 7:36 PM
> To: u2-users@listserver.u2ug.org
> Subject: RE: [U2] access via disabled accounts (solution) - How?
>
How can you pull data from a U2 file, via UniObjects, manipulate it
in VB.NET, and write it back to the file, via UniObjects, via stored
procedures, and without directly accessing the files from UniObjects?
That question contains a heavy duty internal inconsistency.
It you write it back to the
On Fri, Jun 10, 2005 at 10:57:53AM +1000, David Jordan wrote:
> < Thanks
> Will Johnson>>
>
> Within UniVerse Basic is an AUTHORIZE Statement which allows you to give the
> program different access rights to the user running the program. Ie
> AUTHORIZE "Administrator"
In case anybody else i
Hi Dave
<>
A Stored Procedure is just a UniBasic Subroutine. From UniObjects .Net you
would only get data from and write data to the database through the
subroutines (unirpc). The subroutines would have the AUTHORIZE Statement.
You would not use the UniObjects File IO routines.
Ie UniBasic
advance!
- Dave
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of David Jordan
Sent: Thursday, June 09, 2005 8:58 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] access via disabled accounts (solution)
<< Within UniVerse you can do the same thing.
<< Within UniVerse you can do the same thing. You can restrict user read,
write, delete access to the database either setting OS level file access or
by SQL security access. With the AUTHORIZE statement, you can allow
subroutines to have a different access rights. Thus from UniObects one can
In a message dated 6/9/05 5:08:55 PM Pacific Daylight Time,
[EMAIL PROTECTED] writes:
<< Within UniVerse you can do the same thing. You can restrict user read,
write, delete access to the database either setting OS level file access or
by SQL security access. With the AUTHORIZE statement, you
Hi Martin
>The only way that I can see to close this hole is for UniObjects to have an
>option to restrict which operations the client end can request. At the
>highest level, this should restrict the client so that all he can do is
>call
>existing catalogued programs that are compiled with some sp
