Problem With MS Access 2000 Application On Windows Server 2003
Mar 21, 2006
Hi all,
having some serious troubles with a MS Access 2000 project running on a Windows 2003 Server environment.
If I compile the project it doesn't produce a compiling-error. Everything seems to work fine. Creating a .mde file and running it on a Windows Server 2003 produces some serious errors. The project seems to be starting correctly but opening a form or simply trying to close the application causes MS Access to crash! :mad:
I tried the project on 2 different Windows Server 2003 environments, 1 having MS Access 2000 installed and 1 having only MS Access 2000 Runtime installed. Both are experiencing the same problems.
The following references are used in the project:
- Visual Basic For Applications
- Microsoft Access 9.0 Object Library
- Microsoft ActiveX Data Objects 2.6 Library
- Microsoft DAO 3.6 Object Library
- Microsoft Jet and Replication Objects 2.6 Library
- OLE Automation
- Microsoft Office 9.0 Object Library
- Microsoft ADO Ext. 2.8 for DLL and Security
I tried the following solutions to solve the problem:
* Removing MS Access completely and reinstalling it.
* Compiling and creating a .mde on the Windows 2003 Server which has the full version of MS Access 2000 installed.
* Using JetComp to repair the database.
* Creating a new MS Access 2000 application and copy all Forms/Modules into it.
Nothing helped so far..
The same project is running correctly on Windows 98, ME, 2000, 2000 Server and XP Pro/Home. Both Windows 2003 Servers are fully updated, including updates regarding MS Access.
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
Could you please someone take a look int my problem? I have made an Access database with forms, reports and everything. We used it on the LAN and it worked fine. Now I would like to enable users to reach the data even from home, for which I thought the terminal server would be the best (due to mostly slow connection type).
I asked our provider to install Windows Server 2003 R2 on our remote server. Then I installed Access 2003 and copied the mdb file to that server.
The file can be open but it blocks all VBA codes in the forms, modules, etc. I think this is related to the security issues and something called sandbox of Access and tried to follow the instrudtion on the help section, but no success.
Please guide me to run my mdb on Windows Server. Thanks!!
In our company we use a windows 2003 server. Our database is ms access 2002. The back end of the db is situated in a directory on the primary HD of the server. All our workstations use windows professional. The DB works great when inputting data from workstations using widows pro.
I use a vista (ultimate) laptop. It appears that when I enter data from my vista laptop at times it corrupts the backend of the db. None of the other workstations do this. Is vista a problem here in this situation?
I have written a database in Access 2003, saved as an Access 2000 format. This runs fine on Windows XP workstations. When I install the same system on a Windows 7 system, my login screen launches, the user is able to enter in their name and password. Then nothing happens. What is supposed to happen is a form opens up after the password is entered that applies security written in code based on the user.
I have a website that is asp (not .net) based with an Access DB and I am in the process of replacing an old windows 2000 server with a much faster windows 2003 server. Here lies the problem I have a script as part of the admin that exports data to a csv file. The query joins 4 tables together to get the data needed for the export. On the windows 2000 server it takes 1-5 seconds to execute and have the csv file ready for download. On the window 2003 server it times out. I striped it down to use 2 joins and it worked although it took more like 10-20 seconds to export. This exports a specific range of ID's and the range is normally only 40-50 rows. If I put time stamps in the code the problem is in the query of the database, so I know its not in the file write etc.
I am going to rewrite it to use multible querys instead of one large query, but I have many other sites that I am moving to this server that would work better if I can figure out why it is so slow.
The windows 2000 is a 900 mhz server the windows 2003 is a 2.8GHZ server both have 1 GIG of ram. The database file is on the local drive on both servers. I am guessing it is a difference in the Jet version, I just haven't been able to find a solution to the problem. This uses a DSN connection, configured the same on both servers. I have also tried it as a DSN-less connection with the same result.
I have installed access on the server and to execute the command in access it is <2 sec.
I am not an access expert I normally program in .net and php and use MySQL and MsSQL for databases, we just have these legacy sites that use Access DB's
hi im running windows 2000 server and im hosting more then one website from it.. if "members" want to ftp there folder at my server, via the login user name and password that i give them.. but i can not seem to have no more the one ftp site running at any one time, i get an error say that:
The service could not be started because it is not correctly configured. Make sure that its server bindings do not conflict with other sites running on the same machine
what does this mean and what am i doing wrong.... thanks
Hello If the web server is windows 2000 server.there no problem. If I am changing it to Windows xp professtional.I am Getting the following error Error Type: Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0xa34 Thread 0xeb0 DBC 0x1052ed4 Jet'.
While opening a connection to access data base. How to solve it?
I have an Access mdb file that uses linked tables to connect to SQL Server 2000 using a System DSN. The Access database contains many databound forms that are used to update data in SQL Server. Recently, we moved the database from a Windows 2000 server to a Windows 2003 server. After we did this, the Access database would lock up at certain spots in the forms.
We have been investigating this for over a week, and finally realized that it seems to be a Windows 2003 issue. We have tried putting the database on two different servers running Windows 2000 and have had no issues. We then tried putting it on two different Windows 2003 servers, and had the constant lockups.
Our original thought was that there was an issue with the new Jet drivers for Windows 2003, but we looked at the msjet40.dll on both Windows 2000 and Windows 2003 and the version on all is 4.00.9025.0.
Does anybody have any idea on what could be causing this?
By the way, my FO line manager wants an IT report, i am wandering if there is any possibility to search and export users. The report should show in the status column who are disabled, who are enabled, date created and date expired in date column in active directory windows server 2003 environment?
My customer has Access programs that work on their Windows 98 OS PC's, but when they try to use them on Windows 2000 OS PC's they will not work. The programs I believe were originally written in Access 97 and now they have Access 2000 on the PC's.
By not working I mean the following -
The Access program allows them to enter a document name and then the file opens in Word - BUT - when they use it in Windows 2000 it does not open the document at all. It says file not found in Windows 2000 and the file does exist.
** The reason they have Access opening files is that Access keeps track of them for auditing purposes.
Now here is something that I want to mention. On PC's that were upgraded from Windows 98 to Windows 2000 the programs work.
Can anyone here tell me what is missing from 98 to 2000 that would do this.
I was wondering if any of you have had experience firsthand or knew of reasons why an Access 97 database should not be installed on a WIndows 2000 network?
I've installed the windows XP. Also, I have an ODBC connection to ACCESS 2000 database. My scripts are already reads data from ACCESS databse. But it is failed to create new table in database. What may this problem be solved?
My MS 2000 Access application is crashing and returns a msg something like this: "Your Access application caused an error and Access must be closed" This occurs only when I execute some forms; always the same forms cause the problem. Somebody told me to copy the .mdb to another place in my HD and change the names of the forms. I did it and it always works well! Any good reason for that? My app is not yet splited in FE and BE. Splitting would help?
I have Access 2003 in my computer and I have developed an application which I want to share with my co-workers. But they have only Access 2000. Since MDE is only in 2003, I had to convert my 2003 application to 2000. Is there a way to secure 2000 application? I dont want anyone to change my code or import or read my code..I am not sure what is possible..Could someone please tell me how I can do that?
I have a database which is now reasonably finished and am looking slightly ahead at how it can be accessed by the staff. The first clinic has two stations that need constant access to it, namely the clinic area and the reception area.The second clinic is about 3 kilometers distance away from the main clinic and will also need constant access which, I presume,would be by hosting the database on a Windows based Server, to which all three locations would connect and then be able to use the database directly. When I say Windows Server I mean as could be used to host a web site on the Internet rather than use of an internal Intranet system.
Should I split the database and only host the backend part on the server (i.e. the tables)?Does the whole database need to be uploaded to the Windows Server?Is any other software required to make this work?I presume that I would need to introduce record locking? Is this easily done and, if so, how?
I have an access 97 database which all my users will use, back end sits on the server share and is a mapped drive, front end is on the users local drive at present but will become a shared DB on the terminal server.
I can get the DB running by opening in admin mode using the shift key but if I try to run it normally then it just opens access then closes immediately :confused:
Ive checked the event logs and all I get is this..
Faulting application MSACESS.EXE Version 8.0.0.3512
If I enter the DB as admin, then try to run the forms it crashes, is there something in Windows 2003 server that could be blocking them or the code behind them?
I am accessing a SQL Server 2000 database from MS Access. While I can view the tables and can add records, I cannot edit or change them. How do I get around this?
We keep having this error message when a group of our users try to open a MS Access 2000 application resides on a Netware server. "The Microsoft Jet database engine could not find the object 'MSysDb'. Make sure the object exists and that you spell its name and the path name correctly." Have any one seen this error before? How to solve it please! Please advice.
I'm trying to set up an access 2000 .adp project connecting to a SQL server 2005 database. I can set up the connection ok, but once I have completed the setup process, I can the following error messages if I try to creat any new database objects:
If I try to create a new object (a view or table etc), Access tells me that:
'I do not have exclusive access to the database at this time. your changes will not be saved.'
If it's a view, I then get the following message:
'The Visual Database Tools within Visual Studio 6 and Access 2000 do not support some new features of SQL Server 2000. Because you are manipulating an object in a SQL Server 2000 database, some operations will be unavailable to you. In rare cases, you might not be able to save the database object you modified. In other cases, you will be able to save the object, but its previously existing settings for features new to SQL Server 2000 will be lost. In most of these cases, you will be warned if the Save operation will eliminate existing settings or property values.
For a complete description of the interaction between SQL Server 2000 and Visual Database Tools within Visual Studio 6 or Access 2000, see Microsoft Knowledge Base article Q266277, "Using Visual Studio 6 and Access 2000 Visual Database Tools with SQL Server 2000." Knowledge Base articles are available in the MSDN Library Visual Studio documentation or at http://support.microsoft.com/support/.'
To supress this message next time you design a SQL Server 2000 object from Visual Studio 6 or Access 2000, check the following box.
Finally, I get the following error.
'You are connected to a version of sql server newer than sql server 2000. save will be disabled'
Obviously I want to be able to creat and save new objects.
Can anyone help? I've sone some searches on the MS support site, but have not found anything that appears to be relevant.
Hi, I've been working hard at learning Access for past two months and spent a lot of time Googling and speeding through Alison Balter's books and at a slower pace the Paul Letwin’s Developers Handbook set (fantastic but I probably need a year to absorb the incredible detail).
I've built a prototype reconciliation tool using the recommended FE-BE model. I opted for a total ADO solution and have had great success in putting together a fast and useful tool for 10+ users.
I avoided using Workgroups in my design and developed my own basic sign-on authority model which allowed an Administrator (don't confuse with Admin user in Workgroups) to add new users who can use the Access app. The allowable users and which ones are signed on are stored in the BE. This all works reasonable well until network issues occur and the signed on user record on the BE is not reset as should be if the user signed-off genuinely.
This is where I realised I need to be able to monitor who is connected to the BE. There is a way of doing that using ADO which I can get to work. I then noticed because all users are signed on with Workgroup Admin as default I could not differentiate between users. I then decided to implement Workgroup authority retrospectively.
I decided to place the .mdw on the LAN with the BE (this seems to go against conventional wisdom but could not workout how else I could achieve what I wanted to). This enables the two Administrators in different places to maintain users via the FE. I use the /wrkgrp command line flag to point to the correct .mdw.
I then started getting all sort of problems . . .I'm still in testing . . . not so bad but deadlines are looming and I'm worried.
Sorry, I digress. . .the problem I seem to be getting is when I open the FE :
Run-time error -2147217843 (80040e4d) Cannot start your application. The workgroup information file is missing or opened exclusively by another user
I also have problems developing the FE with the workgroup file in place. It seems to complain about another user is locking the FE.
The problem is a little verbose but just trying to paint a picture . . .now, this is what I'm after. . .I need the following ability:
1. Two Administrators who can maintain users. When a new user is added the Administrator chooses a password. 2. When the new user signs on the user is prompted to enter new password. 3. The administrators can view who is genuinely signed on and reset accounts appropriately.
I am currently studying the Access Security sections in the Paul Letwin book to better understand what is going on. It does seem retro-fitting an app to a workgroup model is not straightforward. Admittedly, I should have considered Workgroups in my design before starting (I will know).
Thanks for staying with me if you're still reading . . .any suggestion/pointers would be great.
How unusual is it for a database to become MUCH smaller when converting it from 2000 to 2003 formats. I mean 600megs to 10 megs. And as far as I can tell all the records are intact....!
I have 5 databases running 100% in Access 2000. We are switching to Office 2003 within a couple weeks via an upgrade. What should I do to prep my databases for the switch?
Is there any upconverting tool I need to do ect? Thanks.
how to create web application using ms access. my requirement is i have an inhouse developed retail invoice application ( ms access 2003) which i need to move to web based.
It's not letting me open it since i did it in 2003, and im trying to open it now at home in 2000. I'd really appreciate if anyone can help me convert it and then attach it...thanks :o
