I have a fairly standard db application which uses dataadapters to populate datasets from an Access database. I set up the dataadapters using the wizard, so the delete, insert, and update commands were all created automatically.
I have a few users now who need to be able to view the database, but are not permitted to make changes. I figured if I just gave them read only access to the MDB file, everything would be fine, but now they cannot run the program. They get an error stating that the file is either opened exclusively by someone else ( it isnt ) or they do not have permission. My assumption is that, since the dataadapters are set up to handle deletions, updates, and inserts, they cant be instantiated.
Is that correct? If so, what would be the easiest way for me to make a "lite" version of this app that would allow read only? Id prefer not to have to go through and remove all the dataadapters and put in datareaders. If I just go through the wizard and tell it not to create the delete, insert, and update commands will that take care of things?
I have a few users now who need to be able to view the database, but are not permitted to make changes. I figured if I just gave them read only access to the MDB file, everything would be fine, but now they cannot run the program. They get an error stating that the file is either opened exclusively by someone else ( it isnt ) or they do not have permission. My assumption is that, since the dataadapters are set up to handle deletions, updates, and inserts, they cant be instantiated.
Is that correct? If so, what would be the easiest way for me to make a "lite" version of this app that would allow read only? Id prefer not to have to go through and remove all the dataadapters and put in datareaders. If I just go through the wizard and tell it not to create the delete, insert, and update commands will that take care of things?