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 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 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 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?
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 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.
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 obtained this code from the Net and am successfully using it on a form in MS ACCESS 2002 under Windows 2000. However, all of the string functions result in compile errors and force debug mode when the form is executed under XP Pro (Compile error: Can't find project or library). Any assistance will be appreciated as I am approaching my deadline for rolling this app out on XP Pro systems. Thanks.
Private Declare Function apiGetUserName Lib "advapi32.dll" Alias "GetUserNameA" (ByVal lpBuffer As String, nSize As Long) As Long '----------------------------------------------------------------------------------------- ' This code is used to retrieve the network user name by accessing the API apiGetUserName. ' Created by: Unknown (Found on Dev Ashish web site http://home.att.net/~dashish/api) ' This code has not been altered in anyway. ' Added to database: 27 Dec 1999 ' Added by: Richard Rensel '----------------------------------------------------------------------------------------- Function fOSUserName() As String On Error GoTo fOSUserName_Err
Dim lngLen As Long, lngX As Long Dim strUserName As String
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?
I developed a database in Access 2000 on an XP SP2 machine with linked tables to another Access 2000 database.
Everything works fine using my machine, but when a user running Windows 2000 uses the database, they cannot add a new record to the linked table (either directly using the datasheet or a form). Running a query on the table also did not let me add a new record.
I have searched the MSDN libraries, but I wasn't able to find anything.
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?
We have recently converted from Office 97 to 2003 and Windows NT4 to XP.
In the old days, when I opened a database up I would use autoexec and the db would open to a particular form. On the windows display it would just show that I had a particular Access database open. On windows XP, if I open the database the same way I get two bars at the bottom of the screen showing the objects and the relevant form. This means that all the design is available for people to see.
I am not that clever to have front and back ends etc, so how do I get it to just display the appropriate query / form / report etc.
I hope that I have made it clear. The XP feature showing how many files you have open is quite handy if you want to look at two Word documents but in Access it allows people to fiddle. If they can't see it they can't fiddle with it.
I have an issue with access97 when installed on a windows XP pro sp2 machine. I am constantly getting errors from the vba332.dll module and access shuts down on me. This happens even if I try to go to tools - options on the main menu bar. If any one has encountered this before please help!
This is what I get in the application log:
Faulting application msaccess.exe, version 8.0.0.5903, faulting module vba332.dll, version 3.0.0.6908, fault address 0x000b6614.
Hi, When the user clicks on the file name, I want the form to load automatically & also at the same time minimize the database window (i.e. the window where all the tables, queries etc are listed). Any suggestions?
Hi I've noticed totally different behavior with my secured databases in 98 and in XP.
In XP Access Security works. In 98 it is broken.
For example today I secured a database. I went to another computer running 98 and Access 2002 that was joined to the default workgroup file system.mdw . They still had full access to the database and were not even asked to enter a login. Once I joined the correct workgroup file the security was implemented though. (In XP if I go back to the Default workgroup file the security is still maintained.)
So strange. Where is the security if it is totally ignored on 98 operatings systems? Someone can just make a copy of the database and have full access in 98 despite the database being secured.
Peter.
Hi I've noticed totally different behavior with my secured databases in 98 and in XP.
In XP Access Security works. In 98 it is broken.
For example today I secured a database. I went to another computer running 98 and Access 2002 that was joined to the default workgroup file system.mdw . They still had full access to the database and were not even asked to enter a login. Once I joined the correct workgroup file the security was implemented though. (In XP if I go back to the Default workgroup file the security is still maintained.)
So strange. Where is the security if it is totally ignored on 98 operatings systems? Someone can just make a copy of the database and have full access in 98 despite the database being secured.
Peter.
Then your db is not really [correctly] secured. You should get the same result by copying the database to another computer and the user should be able to open the db without using your workgroup file. Sounds like you have joined your computer to your custom workgroup file [or worse, you have modified the default "System.mdw" file on your computer with your new security settings. Search around the forum for you problem has been asked and answered in many other threads.
ghudson is correct. The behavior you describe occurs whenever you connect to a DB using the default SYSTEM.MDW file. I have answered this question beaucoup times, so look up posts on "Security" where I have contributed comments.
To understand why this occurs, you need to know one more thing: The name of your workgroup is a registry function. You would see the same behavior when you move the .MDB to an XP machine but never join the correct workgroup on that machine. (Because, of course, the registry entry isn't changed until you JOIN the workgroup.)
Your database is not properly secured. Take a look at the Security FAQ document. Search the kb or you may find a link from here.
Why are you double posting?
At least Pat gave you the same answers as your first posting recieved... http://www.access-programmers.co.uk/forums/showthread.php?t=107458
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!!
Please forgive my Newbieness and accept I am a keen ametuer running a small business and trying to use access as a tool. No doubt I will be back with many questions as you all seem so knowledgeable, thanks in advance. Can't really do code but get on OK with built in wizards etc. Wonder if someone might be able to help with this one:
Is it possible to set a command into a form that opens up a windows folder elsewhere on the computer or network? For example, receive email from DIY multiple containing kitchen plan, installation costing etc, as attachments. File attachments in folder on server, manually enter detail into access database which generates "Customer ID Number", decides which fitter, surveyor etc. then need to email a report (have managed conversion to PDF and to launch outlook) but then wanted to copy and attach the original attachments to this new email, along with Access report for forwarding to various surveyors / fitters around the UK. Thus require if poss to open file on server, copy attachments and paste in new e mail, thought it would save time to do by one button press to open server file??
May seem easier to just forward original e mail but unfortunately some of the info in the mails from the DIY multiples is not for distribution and filtering isn't possible.
Perhaps one simply can't do it but worth asking, thanks again. Paul
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 want to have a MS Access 2000 database open, load a Form with various option buttons on and get Windows Media Player to play a MP3 music file. However, when I click a option button on the Form I want the music to stop.
Hi, WHen I used Windows task scheduler to start my application, and then close the application normally, the application closes but Access is left running, still visible in the task bar. The only way I can get it to close is by using task manager to kill it. I found an old KB article ( # 246953) that hints that this (or something like it) is a known bug in Access 2000 but supposedly was resolved by an Office 2000 service pack 2. But I am already running Windows XP, SP2. Anyone else having this problem? Any workarounds?
