Please Help With Access 2000 Locked-out Open Problem!
Apr 21, 2005
I greatly appreciate your help on 2 issues:
1/ At work, I have Access 2000 application residing on a Novel server for multiusers purpose. Everyday, occasionally, the application is locked out by whoever opens first (I think?). Some of other users could not open it since it has the message like "locked out by a particular (computer name)...". Therefore the user of that computer name needs to close the application so others can open it. This issue is not happen in Access 97 as we used that version before and it is not consistent happening, so I could not find the pattern or know why?? Please let me know if you have seen this problem and how to prevent it...
2/ Do we have a way to trigger or initiate GroupWise email inside an Access 2000 application. For example, if a purchase order is created in Access 2000 application, I want to email a co-worker...OR it can be automatically sent an email to my supervisor for notifying the purchase order so he can approve it?
Thanks so much in advance for all the helps...
Access2k
I have MS access database. The database is password encrypted. I do not own this database but it is critical for me to see the contens of this database. I do not want to edit the contents.
We have an old Access 2000 db that is used by most of the company. I also have users who use it via a windows 2003 terminal server. I just created a new win 2008 remote desktop server and installed Access 2000 (What a pain that was).
Now from access, if I go to fileopen, navigate to the DB server and open the DB, it works fine. If I create a shortcut to the database on the desktop of the remote server, nothing happens. No error, no warning, no nothing. It's weird.
If I place a copy of the db locally, it opens just fine.I also tried mapping a drive to the db server and then made another shortcut and still nothing. I also created a shortcut and entered the path like this:
I have a database that currently has security in place so that users input their own usernames and passwords to access the database. The users have recently been added to a windows 2000 server and I want to be able to use their windows 2000 server logon credentials to provide them with automatic access to the database. Is there anyone out there who knows how to set this up? It is a rather urgent request if you could get back to me either on this forum or via email
I am opening and closing a series of Excel 2000 Workbooks using Access 2000 VBA and want this sequence to be able to complete without any human intervention.
However, there are 2 instances when this stops and waits for a human option to be selected:
1. When the spreadsheet is password protected 2. When the spreadsheet has automatic links I get the message:
"The Workbook you opened contains automatic links to information in another workbook. Do you want to update this workbook with changes made to the other workbook?"
How can I code it so that in situation 1 it skips this file and in situation 2 it automatically defaults to do not update?
If I have a report in MS Access 2000 generated based on the criteria selected of a project with work order "9999" with the labor costs, materials costs and the Totals of each crew1, crew2,... and I would like to have those expenditures populated in corresponding cel in Excel for each crew, HOW would I do it?
To think it out loud, could I create a button on a form, so when I select the criteria for the work order, and when I click the button, it should refresh/update the Exel file with the new data...?? How do I write VBA code for that...?
I've created a database of our customers and the plan is to have a few of our members of staff working through it doing support calls - there's very little information to get written to the database - just a flag to show whether the customer has already been contacted or not.
The problem I'm having is that as there's a set call order, and as we're going to have multiple users working through it, there's nothing there to stop 2 or more users having the same record open at the same time and customer getting called more than once. I've looked into the built in access record locking, but that is not going to help much as it doesnt seem to prevent the same record being opened more than once - it just prevents them being updated.
Ideally I want the database to set a flag when a record is opened and unset it when the user moves to next record, and have the form I'm using to browse the records just skip flagged ones. However I have no idea how I would go about doing this as I've pretty much just started writing access.
I have recently been doing a conversion for my boss for a access 2000 database (both front and backend) to a MSSQL backend.
I finished the conversion today (as quite a lot of the code / queries ran slow due to access running the queries locally rather than on the server). And tested it on my and my boss's machine with no problems so he gave the go ahead to update everybody to our new mssql 2000 backend with the modified frontend.
This is when the problems started; We had two different sets of forms for accessing one of our databases systems - the log system, one is the original dynaset based form, and the other is a newer set which uses snapshot views and preforms updates via queries. Nobody uses the old dyanset system apart from my boss and one of the administrative team as they have things on that window which they need to see. About 30 minutes into the release of the new database the system frooze up on my bosses computer and nobody could create a new log (the server was timing out). I assumed this had something to do with the old dynaset's creating locks on the table.
I offlined the database and kicked everybody out of the front end, turned it on again and tied again, this time banning everybody from the dynaset system. Within 10 minutes another computer frooze up, again with a timeout on the insert query. I discovered that after you had added a new log to the database it would timeout on all subquent additions (something it hadn't done during testing) . Further investigatiion showed it was the snapshot list window causing the error, so coded the add log window to close the list before preforming the insert query and then reopen it afterwards. This allowed my machine to make multible additions without flaw. So I released a new client to everybody. 15 minutes later it was timing out again, but this time there you could not even make one new record.
I checked for locks on the table though the server management table and couldn't find any for the Log table. I have restarted the SQL server box and with no avil. So I reverted our backend to the access mdb file and told people to use the old client.
I am at a complete lose to why this is happening, if anybody has had any expericences like this or knows the cause please tell me.
Some information on the database in question.
It was made as an access 2 database all intergrated into one file, then it was seperated into two files (frontend and backend). Upgraded to Access 97, then to 2000 before this final update to MSSQL 2000.
The log system has two main tables. The first is the log title / info table which links (one to many) to a log entry table. This problem only occurs on the main log table and does not appear to be reoccurring anywhere else within the database. The main log table has just under 18,000 rows in it.
:eek: security levels were set on a database using the wizard, unfortunately the person who set the security did not print out the sheets with the WID etc on it, this person is now unable to open access at all from their pc it asks for a password which the user does not believe they set or if they did set one it was their standard pc log in, however the database and access can be opened from any other pc on the network......can anyone out their help...thanks
I copied Odun's post below to describe my problem. I'm having the same problem. I can't even creat a new blank database without being prompted for my user name and password, which aren't working.
Any suggestions would be very much appreciated.
Thanks, Mike
------------------------------------------------------------------------- #1 02-13-2006, 04:33 AM odun Registered User Join Date: Apr 2005 Posts: 108
can't log on to database
Hi all, I was playing with passwords for one of my access db. I tried opening the db with the password, but it won't work. So, I thought I forgot the password. I checked some posts on this forum that helped in retrieving the password and it's the same that I have been trying. I am not sure if the Name is correct, is there a way to retrieve the log on name?
I also noticed that when I try opening any other db on my system, it asks me to log on, I though I was only applying a password to one file.
Please help
Thanks!
odun View Public Profile Send a private message to odun Find all posts by odun Add odun to Your Buddy List --------------------------------------------------------------------------
Is a moment of desperation! I created a security group or something (dont know what i was thinking!), and now there is no way to get into my application!!!! It says to contact with the administrator, but I'M the administrator!!!!
Any way to get the scripts minimun from the applications?? The classes, the modules??? God!!!! My last backup was 4 days ago!!!! I can't loose everything!!
Message: you do not have the necessary permission to use myapplication.
I have an access application which is locked for edit. When ever i open this application it shows me the main menu, i want to edit this menu but it does not give me any option, even the Access File menu and toolbars are not visible. Please help
I have a MS Access 97 database that seems to be locked. I wish to update it but I cannot open it as a regular file. When it is opened, there is no way to edit the database or access any of the controls that are usually present. The tool bars are even different.
I am using OLEDB to connect to an Access DB and it does use the "admin" account as the default user to connect from within Access i.e. this is not a Windows account.
I have an ASP.NET web page that is trying to do a compact and repair using a jet/MDAC object called JRO (Jet Replication Object).
The problem is whenever I call the JRO object I get this error:
"You attempted to open a database that is already opened exclusively by user 'admin' on machine..."
If I try and delete the .ldb file it is ofcourse locked. I found that if I do a CTRL-ALT-DEL and end the aspnet_wp process I am then able to delete the .ldb file and then successfully execute the compact and repair from the ASP.NET web page.
The aspnet_wp process when ended simply restarts itself (a new instance no doubt) and in doing so cannot remember it had a lock on the access db.
My conclusion is that the aspnet_wp process locks the access db file for or on behalf of the "admin" user in the access db.
Even if all connections have been closed the aspnet_wp process has a lock on the database file!
I am still searching for a way to tell the aspnet_wp to let go of the access db file!
I did use getprocessbyname() from the ASP.NET page to try and kill the instance of aspnet_wp programmatically and try and force it to forget by starting a new instance of itself, but ofcourse IIS gets really upset and won't let me kill this process from an ASP.NET page because I figure that in this case its suicide and aspnet/IIS won't "kill" itself but would be happy to "kill" other processes.
Anyway, I would have been content with the "kill the aspnet_wp process instance" approach except it won't suicide.
Does anyone have any idea how I might tell the aspnet_wp process to let go of the acccess db file?
By the way, I found the only account you need in a dev environment is the ASPNET account with read/write access and also your own account if you want to browse the folder yourself. No other accounts needed.
Any ideas appreciated.
I think this one has me beaten
from howartthou Windows XP Prof. VS.NET 2003 IIS 5.1
Basically, I have 3 forms which have all got the properties set to DISALLOW right clicking on them to prevent users accessing the design of the form, they all have code behind them so that they cover the entire screen and block ALL menus/shortcuts apart from those available on the form and I have set up a command button on each form which is password protected to ONLY allow Admins to access the design/backend of the form/database when they enter a valid password.
However, I was playing around with the settings of all these forms and have inadvertantly locked myself out, the last thing I remember doing was setting up a "Password" form to collect the Administrator password which had code attached to allow access to the database design. This was working fine until I tried "tweaking" it and now whenever I input the CORRECT password, I get the error message;-
"Error 2585: This action can't be carried out while processing a Form or Report event"
If I enter an INCORRECT password, I get the standard "Login Failed-Please try again" form that I have set up.
The "Password" form doesn't have an override/Cancel (I wanted to make it REALLY secure) it means that although I can use the database fine for entering/editing information/data within the database when it first opens, as soon as I want to make changes to the design and try to log in with "Admin" privellages using my custom made "Password" form, it then pops up with the password screen and goes no further.
I do have a backup of this database BEFORE I set up the "Password" security to collect the "Admin" Password but I can't remember the code I used and although I can work it out again, it will take me a LONG time to work it out again. So I was wondering if any of you might have some ides or a workaround I could try to gain back "Admin" rights to my database.
Does this makes sense? As stated I do have a backup so if all else fails I'm going to have to try to remember how I got it working in the first place BEFORE I cocked it up but if any of you could save me the trouble that would be very much appreciated!
I've just tried adding the Administrator to a workgroup as described in http://support.microsoft.com/kb/918583 and now I can't open any access databases at all!
It's asking me for Login Details even on a blank database.
I have a table which is linked to a form which has been working fine for over a year now but yesterday the table "locked" for editing. I can now only copy data from the table. The editing functions delete, cut, new etc are not working, we can still filter the data.If we enter data on the form it creates a new line on the table but we cannot edit directly from the table.
I have two database applications and they are: - the (A) application is for administration use. - the (B) application is for normal users use.
the idea is that: I made the (A) application for administrators who have full control over the database objects (tables, forms, queries, and so on ...).
the (B) application I have created for normal users who will have only to use forms to insert some data and display data only.
but the two applications has a respective table called "vacation request" table. where I linked them, so the both administrators and users can share the data.
The real question is that: How can I prevent the users from seeing the database objects in their application. I used the database options which have helped me in hidding the database objectives when the users open the application, but unfortunately they managed to access to the database objects by pressing the special keys.
I would like to have an access to the (B) application when I want to make some modifications to the forms and then lock it from users where they only have to use the forms for requesting vacations and view the vacations.
I am working on a massave aplication that has been running in Access 2000, but recently several of the file sharing users have installed Access 2003 because of the limited availability of Access 2000. All the users are using the same file off the server.
The problem we are having is that when we reference a subform in the "[Forms]![FormName]![SubformName]![FeildName]" Access 2003 does not recognize it and returns an error. I have found that if I will modify it to "[Forms]![FormName]![SubformName].[Form]![FeildName]" it is recognized in both 2000 and 2003.
To try and change every instance of a subform reference will take forever and I am garuteed to overlook something. We reference subforms all over our program, missing any one of them would be a disaster. Before I went to the tedious task of looking through everything I just wanted to throw the situation out there and see if any of you had any great ideas on how to get it fixed efficiently. I would apreciate any ideas.
I upgraded a 2000 db to 2003 recently. When I ran the function below it gave me an error on the line in green. Any thoughts? Thanks. Const FIRSTROW = 13
Dim wsp As Workspace, dbv As DAO.Database, tblResolve As DAO.Recordset Dim tblVchs As DAO.Recordset, tblImpTmp As DAO.Recordset Dim ObjXLApp As New Excel.Application Dim FileToOpen As String, WhereCriteria As String, ImportTemp As String, tmpVch As String Dim TotalDupes As Integer, TotalGood As Integer, TotalRejects As Integer Dim TotalBlank As Integer, R As Integer, C As Integer Dim BadSheet As Boolean, ImpFail As Boolean Dim tmp, tmpType, tmpCtr, tmpRsn
If Forms![Import Block Vouchers]![Import Program] = "0" Then MsgBox ("You must select a Program to load.") ObjXLApp.Quit 'Exit from MS Excel Exit Function End If
I've created a database in access 2003 with the default file format being Access 2000. Everything works fine on my computer and many others, all of whom are running different versions of access (2000, 2002 & 2003).
I have not had any problems with this database until recently and in the last few weeks we have had 2 users, both of them being Access 2000 users who have had the same problem.
The problem they are having is that when they click on any of the switchboard items, the buttons depress an then come back up again when the cursor is moved away, but nothing else happens - no action, no error message - nothing!!! Its the same for all of the buttons on the switchboard.
Does anyone know what is causing this? I have another computer with Access 2000 on it and this works fine, as it does on several other computers runiing Access 2000, I just cannot understand why it is not working on these 2 particular machine.......
I have recently installed access 2003 w/access 97 installed both are on my hard drive. When I create a new db in access 2003 it saves it in an access 2000 format. Does any one know why it does this?
