|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Help! Corrupted DB? error 3110from a novice developer with no security skills.... Not sure what happened, but have a database with just 3 users. everything was fine until a little while ago. Went to open database and no longer had access to the queries that I had created and receieved the following message: Could not read definitions; no read definitions permission for table or query <name>. (Error 3110) The queries were not showing up either, but I did find out how to unhide them. Now they appear "ghosted" and will not let me modify the permissions. Current owner for all "missing" queries is listed as "engine". Two forms are also unavailable and are listed with ~sq_c or sq_f attached to them. This occurs for a Main form and the same main form with its subform: ~sq_cMyMainform1~sq_cMySubForm ~sq_fMyMainform1 Lastly, the Relationships previously established have been completely hosed. Last backup was two days ago so we can restore, but wold like to know if it is salvagable and also what might have caused this. Anyone have any ideas based on the info provided. Thanks for any insight you can provide. Might or might not be the cause of your problem, but: it is commonly
believed that having multiple people using the same MDB file simultaneously, can lead to corruption. To avoid that situation (and for other benefits), people normally use a so-called "front end/back end" structure (FE/BE) for a multi-user database. The BE database contains only the tables. The FE database contains everything else, plus /links/ to the tables in the BE. There is one BE for everyone, but a seperate FE for each user. Another advantage of that structure is that you can easily upgrade the FE's with new versions of the forms & reports, without over-writing the data that has been entered to that point. As I said, this might or might not have been the cause of your problem. HTH, TC TC - thanks for the reply.
I've split the database as recommended. Question. If the BE resides on a server, should each user have their own desktop FE (correctly linked to the server BE) or a copy of the FE on the server. Just wondering how I would update the fornt ends easily if on their desktops. DD Show quote "TC" wrote: > Might or might not be the cause of your problem, but: it is commonly > believed that having multiple people using the same MDB file > simultaneously, can lead to corruption. > > To avoid that situation (and for other benefits), people normally use a > so-called "front end/back end" structure (FE/BE) for a multi-user > database. > > The BE database contains only the tables. The FE database contains > everything else, plus /links/ to the tables in the BE. There is one BE > for everyone, but a seperate FE for each user. > > Another advantage of that structure is that you can easily upgrade the > FE's with new versions of the forms & reports, without over-writing the > data that has been entered to that point. > > As I said, this might or might not have been the cause of your problem. > > HTH, > TC > > Don, I believe that it is ok to go either way. Ie. each user has a
desktop copy of the FE, or, each user has their own seperate physical copy of the FE, on the server. "Happy to be corrected", though. As for updates, there are various "auto FE updaters" out there. The FE automatically checks the server for later versions, & if present, downloads a copy & then replaces itself. If you google on 'auto FE updaters" I'm sure you will find some. In my own auto uopdater, I made sure that the administrator can force the FEs to go /backwards/ (ie. to /earlier/ versions), as well as forwards, if required. Otherwise, if you provide a new version, & that version has errors, you can not automagically restore the previous one! HTH, TC
Show quote
"TC" wrote:
> Don, I believe that it is ok to go either way. Ie. each user has a > desktop copy of the FE, or, each user has their own seperate physical > copy of the FE, on the server. "Happy to be corrected", though. > > As for updates, there are various "auto FE updaters" out there. The FE > automatically checks the server for later versions, & if present, > downloads a copy & then replaces itself. If you google on 'auto FE > updaters" I'm sure you will find some. > > In my own auto uopdater, I made sure that the administrator can force > the FEs to go /backwards/ (ie. to /earlier/ versions), as well as > forwards, if required. Otherwise, if you provide a new version, & that > version has errors, you can not automagically restore the previous one! > > HTH, > TC > > Don did you figure out a solution to the ~sq_cMyMainform1~sq_cMySubForm
problem? I am getting an error like this: The Microsoft Jet database engine could not find the object '~sq_cForm1~sq_cChild0'. Make sure the object exists and that you spell its name and the path name correctly. I have no idea what to start with on this error. Did the FE/BE solution work after you fixed this error, or did you use your backups to get back to the position where it worked and then switched to FE/BE system? Thanks, Parag |
|||||||||||||||||||||||