SQL Application Roles (How to?)

[Randy K]

I'm the SQL Server VBA at my agency. Our Access developers are
starting to migrate the back end from Access to SQL Server 2000 but
keep an Access front-end. The most current project is an new
database with an Access front-end and the initial work having been
done in Access tables.

The application has now been reworked to work with SQL tables. The
programmer decided to look at Application Roles late in the game. It
sounded like a good idea but his front-end spawns additional
connections to the SQL database from different parts of the Access
application. Therefore Application Roles aren't working well.

Is there any reference/resource that details how to incorporate
Application Roles into an Access front-end?

Please forgive, just last year we were all part-time Paradox
ObjectPal programers. Now we are part-time Access programers or DBAs.

Thanks,
Randy K

(e-mail address removed)

 

[Brendan Reynolds]

I have no personal experience of this, but there was a post recently in
another newsgroup by Mary Chipman, who as you may know is a widely respected
author on the subject of Access and SQL Server. Her advice seems to be
'don't do it' - use application roles, that is. Let me see if I can find the
original thread at Google ...

Yes, here it is ...

http://www.google.com/[email protected]

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.

 

[Malcolm Cook]

you probably don't want to

decide after you read this: http://support.microsoft.com/kb/318816/EN-US