By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,827 Members | 2,220 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,827 IT Pros & Developers. It's quick & easy.

SQL Server ODBC Read-Only Connection Problem

P: n/a
Hi,

I have two, similar SQL Server 7.0 databases (in the same SQL Server
Group) that I use as the backend for two Access 2000 front end
applications - one is the live version, the other is the development
version.

The live version works fine. But the other version is read-only, i.e.
no changes can be made to the data in the tables, over the ODBC
connection.

Both systems have similar ODBC connection properties, the permission
settings on the SQL Server databases are the same - users, table
access, database access, etc. The connections use Windows
authenication and the users are set up in SQL Server security logins
with public and db_owner selected.

Has anyone seen or heard of this problem and does anyone have any
ideas on how to fix it?

I appreciate any comments or suggestions you may have.

Thanks,

Chris
Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Does the read-only version have primary keys defined for all of the tables?
They'll be read-only unless they do.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

"Chris" <ch***********@yahoo.co.uk> wrote in message
news:63*************************@posting.google.co m...
Hi,

I have two, similar SQL Server 7.0 databases (in the same SQL Server
Group) that I use as the backend for two Access 2000 front end
applications - one is the live version, the other is the development
version.

The live version works fine. But the other version is read-only, i.e.
no changes can be made to the data in the tables, over the ODBC
connection.

Both systems have similar ODBC connection properties, the permission
settings on the SQL Server databases are the same - users, table
access, database access, etc. The connections use Windows
authenication and the users are set up in SQL Server security logins
with public and db_owner selected.

Has anyone seen or heard of this problem and does anyone have any
ideas on how to fix it?

I appreciate any comments or suggestions you may have.

Thanks,

Chris

Nov 13 '05 #2

P: n/a
Thanks very much. That was the exact problem (and solution).

Chris

"Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote in message news:<1e********************@rogers.com>...
Does the read-only version have primary keys defined for all of the tables?
They'll be read-only unless they do.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

"Chris" <ch***********@yahoo.co.uk> wrote in message
news:63*************************@posting.google.co m...
Hi,

I have two, similar SQL Server 7.0 databases (in the same SQL Server
Group) that I use as the backend for two Access 2000 front end
applications - one is the live version, the other is the development
version.

The live version works fine. But the other version is read-only, i.e.
no changes can be made to the data in the tables, over the ODBC
connection.

Both systems have similar ODBC connection properties, the permission
settings on the SQL Server databases are the same - users, table
access, database access, etc. The connections use Windows
authenication and the users are set up in SQL Server security logins
with public and db_owner selected.

Has anyone seen or heard of this problem and does anyone have any
ideas on how to fix it?

I appreciate any comments or suggestions you may have.

Thanks,

Chris

Nov 13 '05 #3

P: n/a
Hello Douglas
Can you please elaborate about this problem? i havent encountered
this problem which eventually came to my observation only after your
reply. Is it due to design considerations of a database?

Regards
Debashish
Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.