I have installed Office Pro 2003 on a computer that we use as a server. The product was installed for about 2+ years and worked great. Recently we installed a trial version of office 2007 pro to check compatibility with our system.
That has resulted in the 2003 programs acting strangely. Ultimately, we uninstalled 2007 and 2003. Upon reinstalling 2003, everything works great - except for Access!
Running the MSAccess executible simply results in a brief hour glass and then nothing. No processes even register in the Task Manager.
I posted a question the other day http://www.access-programmers.co.uk/forums/showthread.php?t=143027 about not being able to open an Access 2003 database in Access 2007. It was asking for a password when I hadn't set one.
I gave up on that, started from scratch at home on Access 2007 last night and then saved the database in Access 2003 format. Took it to work on my USB drive today - where we use Access 2003 SP3 - tried to open it and had a message pop up saying that the database was an unrecognised format, or words to that effect. This is bugging the heck outta me!
I'm really beginning to suspect there is a problem with Access at work. Our IT guy downloaded the hotfix suggested by Moniker, but I can't see if it made any difference.
I've taken a fresh copy of my A2007 database, saved it in A2003 format again and attached it as zipped file below. Can someone just please see if it opens properly on their PC? It's very rough and ready as I only spent about an hour on it last night, but I just need someone to tell me if they can see the tables, forms etc.
- If you CAN open it, then I've got some evidence that there's a problem at work and can maybe talk our IT dept into a reinstall (or a new PC)
- If you CAN'T open it, then I must be doing somethnig wrong here and I'd really appreciate further advice.
Not sure if this is the correct forum but its worth a shot.
When I try to open any database, MS Access will hang if there is already another instance msaccess.exe running. I even tried opening two newly created blank dbs with the same result. Has anyone ever come accross this behavior?
I have tried repairinging/reinstalling/checking and unchecking "Windows in Taskbar option"
I have a access 2003 database, and i am wondering if i can't setup a search function in a form that will open a file in windows explorer?
What i would like to do is have a test box that i enter in a number for example: 1234 then have a button named "Search" hit that button and it opens a corresponding file in windows explorer named 1234, or just opens that folder directly..
I am designing an application in Access 2003 and it's pretty much working now.
I have a main form set to automatically open (through database startup).
sometimes, access disappears before even showing the form. The ldb file remains in the folder and access does not show up in Tasks (so it's really terminated).
I do have On_Load event code in the form, but nothing drastic and I went through and made sure that all subs have Error Handlers.
It doesn't give me any error messages, just disappears. This also happens when I try opening the main form from the open Access app, but not as often.
Usually, if I open by holding Shift, enter the form in Design view and close it, it then opens no problem.
Any ideas? I searched and googled, but to no avail.
I have installed Microsoft Access 2003 and Microsoft Access 2003 Developer Extensions. I can create Access application by using the Package Wizard. But after I upgrade from Microsoft Access 2003 to Microsoft Access 2007. I can't use the Package Wizard.
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've been using the following code successfully in Access 2003 & now I need to migrate to Access 2010. The purpose of the code is to use the items that the user selects in the list box to build the criteria of a query. Access 2010 keeps giving me a syntax error when I try to run the query & I don't know why:
My code is:
On Error GoTo Err_Command151_Click
' Declare variables Dim db As DAO.Database Dim qdf As DAO.QueryDef Dim varItem As Variant Dim strCriteria As String Dim strSQL As String
[Code] .....
The syntax error I get in Access 2010 is:
Syntax Error in query expression 'SELECT * FROM qryContractListSummarybyDateContract3TYPEBREAK WHERE qryContractListSummarybyDateContract3TYPEBREAK.Rep ortableName IN('Adbri Masonry NSW');'
Attached is a screenshot of the relationships in a database I built a couple of years ago. It's worked absolutely fine in Access 2003 and currently has over 18,000 customers with associated information in it.
However, when I open the database in Access 2007 the performance is awful. All the forms are very slow to respond when tabbing between form elements. I've experimented by reducing the number of form elements calling on related data on a given page and whilst this improves performance it reduces usability - something I don't want to compromise on especially since Access 2007 should be able to cope with this.
My next question is therefore whether I've got the most efficient underlying table design and I can't see any other way of doing it than my current method so I'd be grateful for any feedback or advice anyone has.
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 have an Access DB that I created in Access XP. It works perfectly when used in Access XP. When used in an Access 2003 environment some of the functions don't work anymore. I have users who use Office XP and users who use Office 2003. Does anybody know how to make this DB work in Access 2003 without having to do wholesale code changes?
I have already changed the security to "Low" to bypass the security feature built in in Jet 4.0 but it didn't help. I might have to uninstall Windows XP SP2 to make it work because I know that the application works in an Office 2003 environment with Windows XP SP1 only. But I'm trying to avoid having to uninstall XP SP2 because it's a pain. Any ideas would be greatly appreciated.
Thank you.
My workstation environment is as follows:
OS: Windows XP SP2 Office: Office 2003 SP1 Jet: 4.0
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?
I have two questions related to deplying an Access project I have been working on.
1. I started developing the project in Access 2000, but midway upgraded to Office 2003 and so the remainder of the project has been developed in Access 2003. Things seem to be fine, except that in the top most title bar, after the project name, there appears the following text:
xxxxx: Database (Access 2000 file format)
where xxxx is the name of the .mdb file.
Why is this appearing and should I have done something or do something to make it a Access 2003 format?
2. I am at the point of deplying the db to a small group of users (about 5). Some of them may have Access 2000 or Access 2002. Should I be doing something in particular to make sure things work in their machines. Any pointers to what may be problems or what I should do will be much appreciated.
A few years ago I’ve made an access database on access 2000. The problem is that now I’ve installed the office 2003, and I can’t make the database work properly.
At first says that are missing those files: “tshoot.ocx”, “msioff9.ocx” and “msowc.dll”; so, I’ve copy them from another computer using office 2000 and now only complains about “msioff9.ocx” saying that my database contains a reference incomplete to it.
Is there no other way to convert my database do work properly with access 2003? What can I do?
I have an Access db that is going to be shared by two different users. One user has Access 2003 and the other has Access 2002. Will there be any problems using this setup if both the users are accessing the MDB file at the same time?
Background Info: I developed our main department's Access 2003 split database which is on a server for 15+ Users. I've now been given Access 2007 for development -- Users still have 2003. There are also 2 other smaller databases that are not split (.mdb).
Problem: In the split database, I've saved the Application .mdb as 2003, relinked and made a new .mde. But the Users still cannot open the database. (I did this in a copy until I figure out the nuances with 2007.) The 2 other unsplit databases can be saved as 2003 version and Users can open OK.
I'm grateful for any suggestions on working with Access 2007. I've been trying to tackle the ribbon which is a whole other question.
I have an Access 2000/2003 database which opens up and displays correctly in Access 2007, but when I go to use the File>Print command, or for that matter any of the other pull down menu's nothing happens?
Has anyone else experienced thisproblem, or does anyone know what I am doing wrong?
The company I am consulting with uses Access 2000 and has no intentions of upgrading. I currently do not own Access on my laptop.
I was planning to purchase Access 2003 for my laptop but am concerned that files I create in 2003 might not be "editable" in 2000 even if I choose the 2000 format when creating new databases.
I'm just wondering if anyone has tried creating a file in 2003 (using the 2000 format - as I'm told you can choose what format you want to use) and then edited it in 2000. I want my client to be able to edit the files in 2000 once I've moved on. (I can get 2003 for about the same price as 2000 - so my preference would be to get 2003.) The other obvious reason for going for 2003 is that I could run into the reverse challenge if I own 2000 and my next client uses 2003. At that point, I'd be forced to upgrade to 2003.
My databases are not complex - but do include some customized macros.
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?
is there a way to have both Access 2010 and 2003 exist peacefully on the same desktop. My company uses Office 2010, but my department has an Access 2003 application. As a result, I have to have A2003 on my desktop and use it quite frequently for this one application.
I have some small databases that I really want to move onto A2010 so we can take advantage of SharePoint functions, etc. Is there anytning I can do to be sure that the .mdb and .mde open in A2003 and the new .accdb opens in A2010, without getting errors and the Windows installer going through the Office installation process for the respective version? I've gone to the file locations and set the "Open with" setting to the respective version.
I have one Project in Ms access 2000. If I create Setup(Package) it's working fine in Access2000 but for Access 2003 I need to install Ms Access 2000 Runtime. Kindly tell me how to install Access 2000 Package in Access 2003 without installing Access 2000 Runtime. Can it support backword compatibility ?
Ran into a major issue today with MS Access 2003, or at least the .ADP projects.
I have a .ADP database that has a Stored Procedure as its record source. Once the user selects from the first drop down list box, many of the fields on the form are automatically filled out, and then the record is saved by using...
DoCmd.RunCommand acCmdSaveRecord
This works just fine in MS Access 2000.
With the very same file (the 2000 version) and also on a Converted version, I am receiving an error through MS Access 2003.
As soon as the acCmdSaveRecord code is run I receive the following error...
Run time error '16389'
Reserved Error
[End] [Debug] [Help]
I then select [Debug] and it takes me to the acCmdSaveRecord line of code.
In the code window, when I click [>] to run the code, I get the error...
Run time error '2046'
The Command or Action 'SaveRecord' is not available now.
[End] [Debug] [Help]
Has anyone run into this, and if so is there an easy work around?