Mike, Am I missing something here or is my email getting screwed up? 1. The message header on this message doesn't relate to the message I thought you gave an answer to for Kam.
2. I don't seem to have seen a message from Kam saying what error he received i.e 1709 or did you just pick that one out with a) experience or b) good luck! I'm off ill at the moment so it could just be the effects of the meds! Dave Crozier -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike yearwood Sent: 17 October 2007 13:08 To: [email protected] Subject: Re: ProfoxTech Digest, Vol 53, Issue 68 > Message: 1 > Date: Tue, 16 Oct 2007 14:59:47 -0700 > From: kam <[EMAIL PROTECTED]> > Subject: VFP9 Error: database object is being used by someone else > To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > This is multi-user software with thousands of installations. All seem to work fine with no problems related to having multiple > simultaneous users except: > > We have one client that gets that error message often. They have about 40 users. The files are on a dedicated file server. Many > users access through two dedicated terminal servers. About 6 users are connected locally on the network. > > When they get the error, there really are at least two users in the program so it seems like it is a valid message. Any of the > users can get the message. > Hi Kam No offense, but I thought this was already well known. I'm always surprised by the lack of standardization on best practices in IT. It doesn't matter how many years you have in the industry or how many users run your system or how many copies of it have been sold. You have a problem now and you have to fix it. Error 1709 is caused by multiple users attempting to run a view. http://fox.wikis.com/wc.dll?Wiki~CreatingDBCforViews~VFP There are three solutions: 1 - create a DBC specifically for views and copy it to the local machine - along with the exe - which is also a best practice or 2 - stop using views and switch to an n-tier model with data objects housing the queries which are then embedded in the exe and again copy it to the local pcs 3 - do the least amount of work you can - a bandage - have your error handler - assuming you have one - trap for error 1709 and retry. It may go through. Does not solve the problem, only masks it. Mike [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
