Thanks Paul, That is a great little workaround. i really appreciate your input.
R:egards, Daniel On Wed, Sep 16, 2009 at 7:05 AM, Paul InterlockInfo <[email protected]>wrote: > Daniel- > > Anyway, here's a workaround for MS 2003 SBS: > > First open up SQL Server Management Studio and connect to the database > server hosting the WSS database. Look for the Sharepoint content and > versioning database, by default called something like WSS_Content_<Some > GUID> > > Open a SQL editor window so that you can query against the DB to try and > locate the locked file from the Alldocs table. In my case I was looking for > a locked project file so it was easy enough just to query for the > extension. > > Select * From Alldocs > Where LeafName like '%.mpp' > > The leafname is the file name, so just run whatever clause you need to find > the file, ='<file name>' would be just as good. If your query only returns > one result fine, you know that your where clause uniquely identifies that > record and you can run > > Update Alldocs > set CheckoutUserID = null, > NextToLastTimeModified = null > where LeafName = '<some unique file name>' > > Otherwise use the Id and SiteId of the record of interest and run > > Update Alldocs > set CheckoutUserID = null, > NextToLastTimeModified = null > where Id = <Id>' > and siteID = '<SieId>' > > > This has been a MS-Server users public announcement. <gig> It seems to > time out after 10 minutes and has been documented for over 3 years now. :( > I myself running Linux and MS2003 but the db residing on Linux, I have > never experienced the problem - yet!- till today knowing my luck. Check > the attrib and see for sure and take it from there. Still gotta love MS! > They try real hard 99.99% and things like this is for OUR protection, a > bit annoying at times but so are hackers. JM.02 But this is a server > share > issue. Also you could check ownership from the server, remote in? > release? > Just thoughts, thinking a-load now. > > Sincerely, > Paul D. > > > > > > > > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of MikeB > Sent: Tuesday, September 15, 2009 10:50 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - RE: Rbase won't save "RBE" changes..... > > > You are leaving the file open in the editor while you run it for testing > and > > you have some variables or something screwed up in your code that causes an > access violation. > > I have had this happen in this scenario many times myself and until the > code > > is correct, it will happen again. What I usually do when the save fails is > copy the contents of the editor window to the clipboard (you know Highlight > everything and Ctrl-V), then exit the RBase session, restart, reopen the > file and replace the contents from the Clipboard. > > It is no fault of RBase when you do something that renders the environment > to an unstable condition from repeated snafus. It happens in other IDEs as > well, but it is an indication that you should judiciously run RStyle and be > certain of proper (and timely) variable declarations in your code. Look > for > > old tips on declaring variables in While Loops and the like which are traps > for instability as well. > > > > > > From: [email protected] [mailto:[email protected]] On Behalf Of Daniel > > Lopez > > Sent: Tuesday, September 15, 2009 7:21 PM > > To: RBASE-L Mailing List > > Subject: [RBASE-L] - RE: Rbase won't save "RBE" changes..... > > > > > > > > We are in a multi-user environment. I think this might be the issue some > > of > > the time but i also know that i am in the office alone at times and it > > still > > happens. It also happens more often when i am opening and closing the > same > > file over and over. Making little tweaks and then saving each time and > > running it inbetween. It is not a critical error. I've not lost any data > > over it but It is just annoying as all hell. > > > > Thanks for all the help. > > Daniel > > > > btw....We are using Windows XP Professional > > > > > > > > > > On Tue, Sep 15, 2009 at 3:02 PM, Albert Berry <[email protected]> > > wrote: > > > > If your file is in use by the system, it will be locked. If you use an > > external copy of RBEdit, for example, and you invoke it without closing a > > trace, you will be unable to save the file. The same will happen in a > > multi > > user environment when another user is running the file. > > Albert in the Rockies > > > > > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of > *Daniel > > Lopez > > *Sent:* Tuesday, September 15, 2009 12:26 PM > > *To:* RBASE-L Mailing List > > *Subject:* [RBASE-L] - Rbase won't save "RBE" changes..... > > > > Hey gang. New to the group. Hope you can help... > > > > It seems that almost every time i open a "RBE" RBedit file to make > > changes, > > Rbase won't let me save the changes and i will have to copy my changes, > > completely exit out of the program, start the program and paste back into > > the "RBE". > > > > Any insight would be greatly appreciated, > > > > Regards, > > Daniel Lopez > > > > P.S. I'm using Rbase 7.6 on new machines over a network, having the files > > shared via a server running SBS 2003. > > > > > > > > > > > > > > >
