Setting up Security on a server logged in through Remote desktop

[TJSully]

My Client is considering having his access DBs hosted by an ASP so he can hit them from home and the office. I'm tasked with setting up user level security on these DBs. I think I have a good idea as to how user level security works. When logged into the ASP's server I get an error message when I try to create or join a workgroup. The message is "Access denied" the dialog box's title is Workgroup Administrator. I am able to create a workgroup file, although I get the error message. When I try and join the newly created file I get the error message and am not allowed to join the group. The contact at the ASP tells me I he has "Ok I gave you admin on everything in your user folders, including a reapplication of security on all database files giving you full control to all of them."

I'm assuming the issue is Windows Security on the remote server, Windows 2000 server running Remote Desktop, however I need to eliminate Access it self as the culprit. Is there any issue with Access 2000 and the Remote desktop setup? Are there any additional setup steps involved that I might not be aware of

 

[Scott McDaniel]

I would presume it's an issue with your server permissions ... Access will
work fine using RDC (I use it frequently).

Regarding running your Access databases in a web environment: Are you
re-writing the interface in ASP (or some other web-based technology)? If
not, and you're trying to park your data tables on a web server and Access
them from the client's desktop, then you should warn your client of the
problems assocaited with this method. Data corruption is just about
guaranteed, and performance will be very poor at best. Access (actually, the
Jet engine) is a file server type of database engine. All processing is
performed at the workstation, so if the user requests a list of, say, All
Customers your app will have to pull the entire customer table across the
wire. You can help things along with good indexing and the proper user of
recordsets and bound/unbound forms.

--
Scott McDaniel
CS Computer Software
Visual Basic - Access - Sql Server - ASP

"Smash forehead on keyboard to continue ... "

My Client is considering having his access DBs hosted by an ASP so he

can hit them from home and the office. I'm tasked with setting up user level
security on these DBs. I think I have a good idea as to how user level
security works. When logged into the ASP's server I get an error message
when I try to create or join a workgroup. The message is "Access denied" the
dialog box's title is Workgroup Administrator. I am able to create a
workgroup file, although I get the error message. When I try and join the
newly created file I get the error message and am not allowed to join the
group. The contact at the ASP tells me I he has "Ok I gave you admin on
everything in your user folders, including a reapplication of security on
all database files giving you full control to all of them."

I'm assuming the issue is Windows Security on the remote server,

Windows 2000 server running Remote Desktop, however I need to eliminate
Access it self as the culprit. Is there any issue with Access 2000 and the
Remote desktop setup? Are there any additional setup steps involved that I
might not be aware of?

 

[tjsully]

Thanx for the confirmation on the probability that is it
server side permissions. I figured my issue was security
related, it usually is.

As to the rest of your reply, no I'm not rewriting in
ASP, although that is my day job ;-). No and, perhaps I've
gotten the terminology incorrect. The ASP allows access
via Remote Desktop Web Connection, as I understand it,
this is just the XP version of terminal services. We,
users and myself, will sign into the server, 2K pro, and
execute the access app as if we were sitting at the
keyboard. The only thing sent back and fourth to the
client is the screen shots, correct? The access app runs
on the remote server. I've tested it and all seems to work
just fine.

 

[Scott McDaniel]

You're correct, and RDC is, IMO, the best way to go.
--
Scott McDaniel
CS Computer Software
Visual Basic - Access - Sql Server - ASP

"Smash forehead on keyboard to continue ... "

 

[TjSully]

Yup, it was security permissions that was causing my error messages. Now I just need to figure out how to provide access for users who will have read only Access. Some of my code updates controls as the user scrolls through a record and I get an error 3326