Steve,

Thanks for the suggestion. By default, every table on my database is created by user with active password. Then, access rights are specifically granted depending on who has access to it. So, if the version 7.5 application is resetting the user name to "none," most of my tables would be inaccessible.

So, I just added explicit log-in commands on "On Start Action" option and verified that the user id is now showing up OK within the application.

Thanks for pointing me to the right direction.

James


----- Original Message ----- From: "Steve Vellella" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Thursday, January 07, 2010 1:56 PM
Subject: [RBASE-L] - RE: launching R:Base 7.5 applications


James,

You also may want to check the table you are trying access. If you created
it with an active password then you may have inadvertently restricted the
access to it. Set your user to "none" and try and access your table/form
from the R>.

Steve

Steve Vellella
Office: 520-498-2256
Cell: 520-250-6498

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of James W. Kim
Sent: Thursday, January 07, 2010 9:50 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - launching R:Base 7.5 applications

Hi,

I am currently trying out application designer in R:Base 7.5 for Windows and

came across following issue.

I initially connect to my database using a valid user id and password. Then

I launch my test application in which I try to open some forms or browse a
table. The application comes back with "-ERROR- Unauthorized access to the
table [one of table name] for user NONE (2039)".  Apparently the user
information that I used to connect to the database is not being carried over

into the application environment.

Is there any way I can ensure the user information currently connected to
the database is carried over into the application environment?  Or, is it
something upgrading from 7.5 to 7.6 would solve?

Thank you in advance for any suggestion,

James Kim




--
This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.


Reply via email to