ADP -> SQL Server 2000 no write access until magically touched

  • Thread starter Thread starter Bjorn Mobak
  • Start date Start date
B

Bjorn Mobak

I have a, for me, mysterious problem, with ADP in Access
2002 and Access 2003.

Background:
- SQL Server 2000 SP3a database
- Integrated security
- User is dbo
- Klient is Windows XP
- Application is Access 2003 and 2002

Issue step-by-step:
1. No problems in creating new adp. Data pops up as soon
as I open a table.

2. Adding rows is impossible and the ">*" button is
grayed out.

3. I connect to Enterprise Manager. Open the table and
add a new row. (No problems doing that)

4. Voila, now the adp view of the table allows you to add
data.

My brain is boiling and I need some help here. Any
suggestions are more than welcome.

Bjorn
 
The reason why I don't receive spam is that I'm unable to
type my own mail address :-)

Risking the exposure now hoping that it could relieve
some stress.

Bjorn
 
Hi Kevin, thanks for the reply

Primary keys varies a bit on the example database I'm
using. This doesn't seem to have any influence on how it
acts.

I'm going directly into the tables for this testing and
have no special properties set for these.

I'm looking at the problem from a different angle now and
are looking on the authentication and authorization
sides. (I'm a bit worried that there might be some
authorization issues)

I'm new to ADP (wasn't there when I used Access) What
access rights does ADP require to allow full data access.
Is public, datareader and datawriter sufficient or does
it require dbo rights on the tables themselves?

Bjorn
 
Back
Top