Microsoft Error Code 3051
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 14:04:32 GMT by s_wx1062 (squid/3.5.20)
need permission to open run-time error 3051 - file opened exclusively by another user or u need permission to open rated by 0 users This post has 2 Replies | 1
It Is Already Opened Exclusively By Another User
Follower imm kuwait Since 7/16/2002 Posts 6 Reputation 75 Reply fgh fghjghj (imm) access 3051 Posted: 7/21/2002 5:44 AM rated by 0 users i am new to VB and i developed a vb program on win2000 machine that uses Access database. It works fine on my machine but when i packaged it using PDW ran it on another win2000 m/c it gives me the following errorRun-time error '3051'Microsoft Jet OLE http://answers.microsoft.com/en-us/msoffice/forum/msoffice_access-mso_other/error-3051-exclusive-open-error-on-access-db-and/6839b0bf-4664-4722-8587-d9900d3ba2af cannot open the ......mdb file. File is opened exclusively by another user or you don't have permission to open this file.also, my program does not read Access2000.mdb and i therefore have to convert my acess2000 files to access97 database to be picked up by the vb program.below is the code i've used. dim dbb as database, dns as dynasetDim stat1 As StringSet dbb = Workspaces(0).OpenDatabase(dbFileToOpen)stat1 = "SELECT * FROM http://vbcity.com/forums/t/7242.aspx EMPTABL WITH OWNERACCESS OPTION; "Set dns= dbb.OpenRecordset(stat1$).......sns.Closewhere dbFileToOpen holds the full path and name of the acess97 database. thanks in advance for those who can help me out | Post Points: 20 johnw Clayton, NC Since 4/4/2002 Posts 80 Reputation 850 Reply John Wycoff (johnw) replied on 7/22/2002 8:51 PM rated by 0 users imm, As far as I know the error message is telling you exactly what the problem is. The database is in use. Or maybe its the syntax ant the end of your query "WITH OWNERACCESS OPTION"??? Make sure the database isn't being accessed by someone/something else (including yourself). Then is that seems to be ok try removing the last peice on your query "WITH OWNERACCESS OPTION"Good Luck - John Wycoff- john.wycoff@claytonarea.com- http://www.claytonarea.com | Post Points: 5 imm kuwait Since 7/16/2002 Posts 6 Reputation 75 Reply fgh fghjghj (imm) replied on 7/26/2002 11:15 PM rated by 0 users Johnthank you very much for the reply. the application works now. it was indeed an access privilige issue. Although the error message clearly stated that, it never occured to me to check the access privilges of the .mdb file itself. as the database was copied thro from CD, it had taken up
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project https://www.experts-exchange.com/questions/10227500/Another-Run-Time-error-'3051'-with-Access-and-VB6.html Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts https://bytes.com/topic/access/answers/478237-error-3051-a Exchange > Questions > Another Run-Time error '3051' with Access and VB6 Want to Advertise Here? Solved Another Run-Time error '3051' with Access and VB6 Posted on 1999-11-01 Visual Basic Classic time error 1 Verified Solution 8 Comments 4,096 Views Last Modified: 2013-12-25 I have seen similar questions posed here before, but the solutions presented have not solved my particular problem. I have a VB6 application connecting to a password protected Access 97 database, using DAO and Jet. On a machine where Access is installed there does not seem to be a problem, but on time error 3051 a machine without Access I get the: Run-time error '3051' The Microsoft Jet dataase engine cannot open the file.... It is already opened exclusively by another user, or you need permission to view its data. There are no permissions, other than the default user admin, and it is not open by any other user or application. I am already making sure that the database is opened non-exclusively and is not read only. Here is an extract from the opening code with the password info etc removed (regdata is a data object on the form filled by the following code to pass the password to the database): Private Sub Form_Load() Dim db As Database Dim RegSet As Recordset, growthSet As Recordset, dateset As Recordset 'Create recordset of data required for registration regdata.DatabaseName = "c:\Database\myDB.mdb" regdata.RecordSource = "registration" regdata.Connect = ";Pwd=xxxxx" regdata.Refresh Set db = OpenDatabase("c:\database\myDB.mdb", False, False) Can anyone tell me what I am doing wrong here? Cheers Debbi 0 Question by:debbi_stott Facebook Twitter LinkedIn Google LVL 5 Best Solution byAnswerTheMan you need to install a MS file called "Dataacc.exe" on the target machine. t
get tips & solutions from a community of 418,589 IT Pros & Developers. It's quick & easy. Error 3051 P: n/a rdemyan via AccessMonster.com In 12 months of working on my app, I have never had a corruption problem with the backends, often with the front end but never the backends. So, of course, now that I'm planning to roll a new version of the app out next week, I suddenly had a problem. Here's the development configuration 1) Computer #1 a) Access 2000 - app is developed on this machine b) A Folder on this machine acts as a test server folder for the backends: Backend #1 and Backend #2 2) Computer #2 a) Access 2003 - client plans to switch soon, so I have to test A2003 So today, I suddenly got error 3051 when Computer #2 (A2003) linked to Backend #1. This error is: "The Microsoft Jet database engine cannot open the file 'Backend #1'. It is already opened exclusively by another user, or you need permission to view its data. Backend #2 was linked fine. Computer #1 did not have the app open so there was no other front end attached to either backend. I checked for a .ldb file for Backend #1 and there was none. Yesterday, however, there was major bloat of this backend from 45 MB to 110 MB, so I compacted it yesterday on Computer #1. Today, was the first day that I tried to open "compacted" Backend#1 on Computer #2. As noted, I received error 3051. HOWEVER, A2K on Computer #1 was able to link to "compacted" Backend#1 just fine. I could open "compacted" Backend#1 on Computer #1 just fine, but not on Computer #2 (same 3051 error). Because I've never had a problem with a backend, I'm very bad about backing up the backends. So, naturally, I didn't have a current copy to try. But I did replace Backend #1 with a version that is about 1 month old. A2003 on Computer #2 linked to it just fine. So, I got around the problem by taking the month old Backend #1 backup and deleting all tables in it. Then I imported all the tables from the current "compacted" Backend #1 (the backend that caused Error 3051 with A2003 on Computer #2) into the month old backup. Then I tried linking A2003 on Computer #2 to the backend backup (with the imported current tables) and everything worked just fine. This is what drives me nuts about Access. How am I going to handle this kind of problem when a client has this occur to them without getting personally involved. So, I'm posting because I'm hoping some developers might provide some insight, experience on what they do to minimize such problems. I am including a utility with my app that will use the Windows Task Scheduler to backup the backends nightly, which should help, but I don't see how that will stop this problem. My l