Vista, Ms Access & Windows Server 2003 Corruption?
Apr 3, 2008
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?
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!!
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.
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?
Have been testing installation of Office XP Developer Access 2002 runtime package created using the package wizard on a WinXP Pro SP2 machine, for installation on a Vista RC2 5840 machine.
After installing the latest necessary updates such as Office XP Developer SP1 among others which were essential to remove the Path/File error I had, A new error displayed itself as soon as the runtime install package launched.
------------------------------------------------------------------- Visual Basic 6.0 Setup Toolkit (Error Window Title Bar)
The Office System Pack cannot be installed on this system because it requires Windows NT Service Pack 6 or later. -------------------------------------------------------------------
I assume Windows NT SP6 has no relevance to Vista ???
Maybe some other update will help here. I have googled for hours to no avail.
I have a customer that did not read my recommended hardware specs and bought a Vista machine with Office 2007 preloaded on it.
My application uses a Access 2003 database and it is working fine in the Vista environment. The database utilizes Access security and has a database password.
My problem is that I can't see any data that has been entered! I have ran queries and opened the tables, but it is as if there is no data in the tables. However, my application can still read the data...this is a very weird problem! This is a tech support nightmare!
i'm thinking about upgrading my operating system from XP to Vista Home Basic, but curious if any users have have experianced any dramas running Access 2003 SP3 on the Vista platform? or shouldnt there be any mayjor problems.
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 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
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.
We keep having our backend tables corrupt. We want to upgrade only the backend tables to SQL server. I don't even know where to start. What version of SQL server? I guess I find out if we have an existing licence in the company? Any help on this?
We are sharing an Access 2003 database amongst two departments that contains twelve (12) tables that are SQL Server linked tables. Nine (9) of the tables work just fine for people in both departments. Three (3) of the tables cannot be opened until the user refreshes the link(s) using their ODBC DSN.
We do not understand why nine of the tables work without issue but three will not.
Has anyone ever run into this issue before? Does anyone have any ideas on how to resolve this issue?
Is there an easy fast way to do this: We are having problems upgrading to SQL server for only our backend tables. The problem is we have SQL reserved words that can only be used by SQL Server. There is a huge list I was given. I assume this applies to all objects, in our ms access database. Any suggestions on how to at least 'find' all of these at once? Or fix this easily? I know which tables would not upload ...but in looking through them I don't even see which reserved word is causing the issue???
Also..our front end application with stay Ms access 2003. Do I still need to update any reserved words in that or just the tables?
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
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
I have a vbs-script that opens my access database db.mdb and runs the module "Export":
dim accessApp set accessApp = createObject("Access.Application") accessApp.OpenCurrentDataBase("D:Datadb.mdb") accessApp.Run "Export"
accessApp.Quit set accessApp = nothing
This works fine as a scheduled task on a Windows 7 computer.
Is there a way to make this work on a Windows Server 2008 R2 ? When I double click the vbs-file, the file opens instead of runs. And when I create a scheduled task, nothings happens.
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?
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've been perfectly happy with Access97 and WindowsXP.
But my laptop's circuitboards have deteriorated, and I need a new computer. I'm wondering what the real-world has to say about using Access 97 with Windows Vista. Does it run seemlessly? Please say yes.
I have an application which I've been improving since 1998. I tried a demo of Access 2007, and did not like the way my app interfaced with it, and I don't relish a whole lot of reworking. But I don't want to buy a laptop with an obsolete operating system.
Hi, i have a problem with an access database, well 2 problems. first is i don't know much about databases. the second is at work we installed 3 computers in an office with windows vista o/s. they then had a company come in and install software for their business. They were using office 2000 access database on xp previously. The company installing their software copied the access 2000 database to the vista target machines, i believe they may have converted the database to access 2003 version when doing this. The problem is the database doesn't work and they have called us back in to sort out the problem. Well we installed service packs, fixes, patches etc and googled a lot but found no simlar problems or solutions, in short we are stumped. I think the database is compiled into an app or something with switchboard etc, which i think means i can't access it? anyway it opens up with a logon form to get into DB, i enter the username and password and click ok and it gives a message saying:
"the expression on click you entered as the event property setting produced the following error"
it goes on to say there may be problem with an "event,function or macro"
on vista with office 2003 it lists several possible causes which i havent access to right now.
i have now tried it on my own pc with xp pro and office 2007 and it basically gives the same message as above but the list of possible causes is reduced to this one:
"This error occurs when an event has failed to run because Microsoft Office Access cannot evaluate the location of the logic for the event. For example, if the OnOpen property of a form is set to =[Field], this error occurs because Access expects a macro or event name to run when the event is fired"
Can anyone explain or point me in the right direction of where to get a solution. I think this is something for a programmer to solve and possibly something that the original database programmers should be looking at rather than me. am i right?
I created an Access Runtime Database Download on Windows XP. One of my clients downloaded the db to Windows Vista. The installation went fine and he was able to populate the database with no problem. However, now he needs to send me back the data and we cannot seem to access any data files. The backend.mdb file appears to be blank, even know the data appears on the front end. We have tried searching the computer to find any hidden files it might be saving the data to and there doesn't appear to be any. I have tried copying the entire folder containing both the frontend and the backend to a jump drive and looking at the data on a different computer and it appears to be blank. This doesn't seem to happen on any other OS. Since it is a runtime version of Access, I am not able to export any files or even view anything of administrative value within the DB. When I look at the backend.mdb in Explorer, the modified date is old, so it doesn't seem to be adding the data to the backend, even though it is theoretically linked to it. Does anyone know where this data might reside or of a workaround of how to extract this data???
