A forum for technical support discussion related to Fogbugz.
We are using MS Jet for our FB backend database. Today I learned how I can link the tables from the Fogbugz.mdb file to a new .mdb file on my machine and create my own queries/reports against the FB database without disturbing the Fogbugz.mdb file. To do so I created a read-only share to the accessories folder on the FB server machine to provide access to the Fogbugz.mdb file. As soon as I did this any attempts to modify the FB database through the FB web interface failed saying the database was read-only. Removing the share fixed the problem. I checked the access rights of the Fogbugz user account on the server and everything looks fine. Why does creating a read-only share cause the Fogbugz user account to lose its full control access to the database?
A hunch: you might have opened your reporting database in exclusive mode from your own machine, which would have locked the tables in the backend database. In Access, click the little drop-down arrow next to the Open button in the Open File dialog box and make sure you select "Open" rather than "Open Exclusive".
Of course, if you checked with Access closed and it was the mere act of creating the share that caused the problem, then my hunch is dead wrong.
Saturday, March 19, 2005
Your hunch was pretty close. Sure enough, it is not the share that causes the problem. The problem only occurs when I have my reporting database open. However, I tried using "Open" from the pop-down as opposed to "Open Exclusive" and the problem still occurs. (I think Open may be the default here anyway.) I am still stymied. I wonder if there is some setting in the table links that maybe causes this.
This topic is archived. No further replies will be accepted.Other recent topics