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 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....!
View 1 Replies View RelatedIt'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
Hi, I have a few Access 2003 databases and I need to open them on my computer which has Access 2000 on it. Can anyone please tell me how to convert it so it is compatible? I have looked into "databse utilities" "convert to" etc but can't figure it out.
View 4 Replies View RelatedI have developed quite a few Access 2000 applications for clients and continue to maintain and update these applications. I am starting a new position with a client using Access 2003 at the client's location. I would like to upgrade to 2003 but I still need to service my 2000 clients. Can I install and run both versions of Access or can I still maintain the 2000 apps under 2003? Help!
View 4 Replies View RelatedI converted an MS Access 2000 DB to 2003 with no problems. I am able to open it up in Access 2003 now either by double clicking it or from Acccess - file open. I then created an MDE file in Access 2003, but when I tried to open it up I got a message saying
This database is in an unrecognized format.
The database may have been created with a LATER version of Microsoft Office Access than the one you are using. Upgrade your version of Microsoft Office Access to the current one, then open this database.
I noticed a service pack will get rid of this errror. My question is if I distribute the MDE will the user get the same error if they don't have the service pack installed on their PC? Will my installation of the service pack fix the errror and allow anyone to use the file without getting the message.
Thanks
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 have written my very first database in Access 2003 but it tells me that it has been saved in Access 2000 Format.
My questions are:
1. Why has it done this?
2. Can I change it 2002 or 2003 format?
Hi
At work I was just updated to access 2003. I am trying to update a data base that I created in access 2000. Whenever I try to open a data access page I get the following error. "The installer encountered an internal string error. Installation failed." I've updated the Web components and that seems to have gone ok. My IT people are at a loss.
Any suggestions?
Thanks
John
Hi,
I'm just wondering if there is any differences in writing queries in vba in different versions of access. i'm developing a search function in access 2000, but it doesn't seem to be working. however, the same code in access 2003 works fine.
Here's an extract of the code when the search button is clicked (I'm getting table information, attribute/field information and condition they're specifying from the user. The result is then displayed in a subform):
Private Sub cmdFind_Click()
Dim searchSQL As String
Me.cmbTable.SetFocus
searchSQL = "select * from ENGINEERS INNER JOIN TEL_CABLING ON ENGINEERS.EngID = TEL_CABLING.EngID where " & Me.cmbTable.Text & "."
Me.cmbAttribute.SetFocus
searchSQL = searchSQL & Me.cmbAttribute.Text
Me.txtCondition.SetFocus
searchSQL = searchSQL & Me.txtCondition.Text
Me.subfrmTest.Form.RecordSource = searchSQL
Me.subfrmTest.Form.Requery
End Sub
The part in red is the part that is highlighted whenever i run it in access 2000. The error message is: " You entered an experession that has an invalid reference to the property RecordSource "
Can anyone tell my why it's like that and how i can fix it to work for access 2000?
Thanks I've also enclosed a picture of the form, so you can get a feel of what it looks like.
Kathy
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.
Hello..
I got the following code from this forum to create shortcut on the desktop..
==================
Set objShell = New WSHShell
Set objShortcut = objShell.CreateShortcut(objShell.SpecialFolders("AllUsersDesktop") & "" & sShortcut)
objShortcut.TargetPath = sDB
objShortcut.WindowStyle = "3"
objShortcut.SAVE
=================
I have Access 2003..but file format is 2000 because others have access 2000.
This code works great on my machine..but getting error on access 2000 machine..It does not recognize "New WSHShell" in the above code.
-------------------error message
Compile Error:
User-defined type not defined
-------------------
Any references needs to be added?
Please help...Thanks..
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
Hi,
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.......
Many thanks in anticpation.
Steve
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?
Thanks--Appreciate any help
i am trying to use access 2000 database onto to access 2003. When i try to click design mode to change something it gives me this message:
You dont have permissions to modify.
If i run it on access 2000 it runs fine.
Someone please help.
Hi,
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?
Regards
Hi:
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.
Any help, comments... appreciated.
Thx,
dave
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?
Thanks--Appreciate any help
I have successfully used the recommended way to display images from a folder in a form as posted on the microsoft website.
http://support.microsoft.com/kb/210100/
These instructions were for Access 2000. I noticed that there are seperate instructions for doing this using Access 2003.:
http://support.microsoft.com/kb/285820/
My questions are:
1. If multiple users access this database using different versions of Access (2000 and 2003) will it not work for some?
2. do i have to modify code if i update to 2003?
Thanks for youir feedback!
~Bruce
I have built a rather extensive database using Access 2000. When I install it on an Access 2003-enabled machine, the first time it is opened, the user is presented with the following errorbox:
"An error occurred and this feature is no longer functioning properly. Would you like to repair this feature now?"
At this point, clicking "Yes" results in an update the installation of Access 2003. Then the database must be opened manually again. Then, the following is displayed:
"Module not found."
Closing the database at this point and then opening it again results in a normally functioning database.
I have several questions:
1) What is the feature that is no longer functioning properly?
2) What is updated when the installation exec runs?
3) What module is not found? I assume this is one of the VBA modules that I've created, but I've check all 62 of them and they all seem to be there available.
4) My first guess was a reference problem, but I've checked the references used and all are available, as far as I can tell. These are the ones that I have referenced: VBE6.DLL, MSACC9.OLB, DAO360.DLL, STDOLE2.TLB, MSCAL.OCX, MSADO25.TLB, MSO9.DLL.
5) After getting the first error - the one about nonfunctioning feature, I clicked "no" to the repair now question. This does nothing except the database remains open. At this point, I opened the code and tried to compile, but I get the "module not found error". I likewise tried to set a breakpoint in one of the first modules and I get the same result.
6) I even tried to copy the forms, queries, tables, and reports into a blank database with no references and no other extraneous code and received the same result.
This site has been extremely helpful in the past and I am really relying on you guys again for the same stupendous help now.
Forever in your debt,
Tom
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.
Help...
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.
View 3 Replies View RelatedI 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 ?
Thanks
John
I never realized how wonderful Access 2000 help was until I tried using Access 2003. Last night I went to MS online to see if I could download Northwinds.mdb 2003 database samples...I couldn't find anything. can someone recommend a good Access 2003 Developer's book??
View 2 Replies View RelatedI just got a new machine with office 2003 but it doesn't include ms access. Can I use access2k with this new version of office?? so I can do reports and put them into word etc??
View 2 Replies View Related