September 1, 2004 at 5:28 am
I have a distribution consistings of a Fresh MSDE Install, a database attached to that instance of SQL designed and build in SQL Developer and a newly created Access Project pointing to that database with SA privliges.
The problem I am getting is when I try and edit a table, it tells me that I only have read only capibility on the table and wont save may new records.
I have the same configuration on my computer and it works fine. I was thinking of re-installing MSDE.
Any thoughts on what this could be?
September 1, 2004 at 9:06 am
You need primary KEY field in your table.
September 3, 2004 at 6:12 am
If you are doing this new "install" from a CD, you might need to change the properties on the MDF file and the log file to remove the read-only property.
September 3, 2004 at 6:44 am
Thanks Rookie..
I did noticed that. I am also looking into directory and files rights (for the MDF & LDF files) authentication at the box and also Access at the client is an SP1 instance which need updating to SP3. I'm running MDAC 2.7 and wondering if that is causing some problems as well and might have to bring it down to MDAC 2.5.
On the SQL side, while I did turn off the read-only attrib on the files, I did not detach and re attach the db. Also looking into creating user with explicit rights to database. Im currently in a beta state for the software so I used sa as a temporary measure so I might change that.
September 3, 2004 at 7:53 am
I run MDAC 2.8 and everything is SP 3 for SQL Server.
In my databases that I distribute, I use something like CS_dbo, CS_User, and CS_Admin where CS is the name fo the system (Community Service).
You might have a problem since you did not detach adn attach the files. If you are not distributing data, I would recommend the you create the databse from a script with all the users and rights in the script.
September 3, 2004 at 8:32 am
Thanks Robert for Responding...
I have been doing SQL Server 7 & 2000 work in Application OLTP & OLAP development for 4 years now but this is the first time I have hooked it up to Access. I will probably do this more as I am considerably more fluent in building native SQL Server systems and just use Access for the presentation layer.
Since I am in beta right now, the database is in a state of flux with slight modifications being made to production release. Because of this I am distributing a copy of "my" database with each new major modification release. When its ready for production, I will be creating scripts for all objects, users, and initial static data for "pristine" DB build.
Thanks again for your assistance
"Solid Heuristic views of development lead to good deterministic design..."
September 3, 2004 at 9:08 am
If I remember correctly, it was 3.51 that I started with.
September 3, 2004 at 9:27 am
The path of database product used starting in 1985: Dbase II, DBase III, Paradox 3.05, 3.5, 4.0, 4.5, for DOS, Paradox 1,4.5,5.0,7.0 for Windows with C Parados Engine Library using Borland C ++ in some instances...
My transistion into SQL Enterprise Products started with Sybase 4-10 before moving onto Microsoft SQL Server at Beta2 of version 7. Since Sybase essentially OEM'd SQL Server through 6.5 the transition is quite painless.
Its good to meet another veteran of computing as this year marks my 18 of actually earning an income using them and 27 years since I wrote my first program.
September 3, 2004 at 9:43 am
I was also a Clipper head, and did FoxPro, DbaseIII, MS Access 1 - 2003. And, even co-authored a book on MS Access. I've only been making a living doing it for the last 14 years. Now, I do VLDB design and data warehouse design for a very large garbage company. What irony. 🙂
The funny thing is that I was offered a full scholorship when I graduated in '71 for programming, but I did not want to punch cards, so I did Psychology instead.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply