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?
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'm looking to purchase Access 2002 because that is the version we use at work. The problem is, when I search the net for deals, it is more economical to purchase Office XP 2003 OEM instead of Access 2002.
Is Office XP - version 2002 unless it says Office XP 2003?
Or should I just purchase Office XP 2003 and just convert before I take my database to work? I hear the difference between 2002 and 2003 is mostly the VB coding functionality.
BTW I am looking at the following deal..Hope its not a scam http://www.pricegrabber.com/search_getprod.php/masterid=991291
I have an application which I did in Access 2003 and it uses "Microsoft Access 11.0 Object Library" and also "Microsoft Outlook 11.0 Object Library".
I have converted it to 2002 format from database utilities where it says (2002-2003).
Now when this application is opened in Access 2002 the refrences are "Microsoft Access 10.0 Object Library" and "Microsoft Outlook 10.0 Object Library", now the code starts throwing various errors.
Now what is the way out to avoid these errors? Should I copy the 11.0 libraries and add those in refrences on the machines where access 2002 is available.
I did some initial searching but I am not sure what to search for. I have inherited an access application for maintenance. I am a C# developer by trade so developing code and ui inside the db is kind of weird to me not slamming it, just a little confused with the paradigm. Anyway, I had successfully added functionality to the code base as the per requirements. I made the changes using 2003. No database conversion dialog ever showed so I figured everything was cool. However the client is using 2002 and when they launch it the MDI parent shows the correct title but the form that is opened by default never shows up.
My Access program crashes frequently. I tried the 'Repair Office' function, but that has made no difference. On checking, I see that it's Access 2002, not 2003. Can I still get Access 2003? Should I upgrade to that? I don't want to buy the new Office 2007 suite.
I have discovered a problem with access2003 which is annoying the hell out of me. If any of you out there open up the sample db 'Time and Billing' then go to the preview invoice form, via the clients button on the switchboard, the bottom 4 windows, Total hours, total hourly billing and total expenses give a #Name? error, while the amount due gives an #error? fail. This all works perfectly well in 2002 and I have used it as a basis for a database. Move it over to 2003 and I get the exact same errors.
Does anyone else see these faults and how on earth can I repair them?
I know a bit about using access but I'm not that experienced.
Is it possible that ADO isn't supported in 2002? I use ADO recordsets in a LOT of places...
Is there something idiot-friendly that someone using 2002 can do to register the Version 11.0 object library (ie without re-installing MS Access or requiring the MS Access CDs?)?
Will this issue pop up everywhere that i do non-trivial coding (ie i also use XMLHttp, InternetExplorer.Application ActiveX, etc...
I have written an application which uses a query for the current record and then opens a Word document, merges this record and shows the merged document for the user.
all works fine using Office 2003 - when i try it on a pc with Office 2002 - it diesn't work. Something is happening - WINWORD.EXE is running on the process list. But the document doesn't open. I have added the Microsoft Office 10 Office Library to the references but still no joy.
It's a killer - all testing was done on Office 2003 and now a key user wants to use the app - on 2002 and it doesn't work
Currently my wife has an access 2002 project for work and she would like to work on it at home. We have access 2003, is it possible for her to take the project work on it in access 2003 and then be able to run it again under access 2002? Or should we just look for a copy of access 2002? She can't upgrade the version at work so that's not an option.
Since the last Windows XP update on the secretary PC, all combo lists are now empty even if the related tables are not at all.
Here is her configuration: Windows XP SP 2 Access 2003 SP 3
Here is the description:
1) I've got a combo list based on the table Towns with zip-code, name, country.
2) In the form, in addition the combolist is sorted on the name, just to easily pick up the right Town
3) Since the Windows update, the combo list displays only the zip-code, the other fields are empty even if the table content is not empty at all; I mean I checked in the table content itself.
4) I created a query based on the same arguments of the combo list and the query is working well alone; if I try to create a new combo list linked to the query, then I get the same weird result
5) I've tried to create a new field with the combo list assistant; when I select the table Towns, it shows me the full content (so name, zip, country) and when I run the form, the combo list is again almost empty !!
6) What is more weird is that when I put the Access database back on my standalone laptop which is running Access 2002, the combo list is working correctly !! In fact I am currently maintaining the Access database from my Access 2002 since more than one year and I had no issue
7) In fact, I got the same issue with all the combo-list in my Database
8) I tried to compact the DB but with no effect
Somebody has a brillant idea for me ?? otherwise I think I will contact Mister Bill directly :)
My office is running Microsoft Access 97 but I use voice recognition software and that is not a real compatible with the 97. I need to upgrade to the latest Microsoft Access version.
My question is if I upgrade to Microsoft Access 2003 is there a way for my created databases to be saved so the users of Microsoft Access 97 will be able to open and use the database? I understand they will not be able to make any changes to the database but will they be able to open it/view it entered their criteria into the queries can be able to see their information?
Hi all, I have created a database for work in Access2003. I have two questions. The first is, many people at the work place use AC97 and some use AC2000. In order for everyone to use the database, i have saved it in AC97 format. It seems to open fine in Ver2000 and 2003, but i get this nag screen on load up with these versions saying "do you wish to convert the database". As I'm working off a shared drive, i don't really want anyone converting the dbase. Is there a way to disable this nag screen when loading in AC2000 and AC2003??
Second question, is it possible to have more than one instance of the database open at anytime? . If I've got the database open, my colleague can't open it. Its a simple database that writes records directly to a table. Thanks for any advice.
Having a problem here after installing 2007. All my previously created databases work fine in 2007 (after clicking the enable, which is a pain,but don't know any other way) When I return to 2002 and try to open the databases I get different errors all something like this on....... "The expression On Open you entered as the event property setting produced the following error: Object or class does not support the set of events. Whats up here?????I have found a site here...http://allenbrowne.com/bug-17.htmlMentions this problem,but refers to Vista..... Does the same apply to XP? And which is the best fix?
I have a 2007 db, been working no it in 2007 and occasionally in 2010, careful not to use any 2010 items. Well I goofed and added a Navigation Form (2010 only) and then deleted it. Now My 2007 db opens in 2007 fine, everything works, but the glowering Warning message and lovely yellow yield sign show up constantly. How do you resolve the incompatible items and clear this warning?
I converted an old Access 97 "mdb" to Access 2002 SP3.
I then added an option button within a frame. The problem is the new option buttons properties does not include "Option Value". How do I get this property to show up within the properties?
I have converted a database from 97 to 2002 and now i have getting two errors which are concerned with the relationship. In Access 97 application the relationships are working well but after the conversion some relationships between the tables are broken and now i cant establish the same relationships between the broken tables. I get the erros message
Microsoft cannot establish this relationship with referential integrity
In table X are some recvords which violate the rules of referential integrity.
I wonder the same relationship works in Access 97.
I have created a database using Access 2003. If I leave the database in the MDB format, it will run perfectly on my computer at work that has Access 2002. However, if I use Access 2003 and convert the database to an MDE file, and try to run it at work using Access 2002, I get an error that states "The Visual Basic for Applications project in the database is corrupt."
I know it is not corrupt because the same MDE file runs fine on my machine with Access 2003.
I would like to share the database with some fellow staff members, but I would like it in MDE form.
I need to develop an application that works in 2002. I tried to take a 2002 mdb, convert in 2002 to 2000 and try it on my machine at home. It didn't work and I couldn't find the missing reference. I then took an mdb that was originally a 2000 format, converted it to 2002 and it worked fine. So what I want to do is develop the app in 2000 and just convert it over to 2002. This allows me to work on it from home which is pretty important since my deadline is creeping closer. Am I ok doing this or am I courting disaster? Or is there another way of doing this?
I have no problems creating an MDE file from a newly created database but the system hangs when I try to do the same with a former Access 2000 database that I converted.
I am creating an access database and I want to know the following limitations;
1. Maximum number of users who can log into the database at a time
2. Maximum size of the database. Here I understand that it is 2GB, but I am confused as to whether it is for .MDB file or for each table in the database.
I have an existing database using access 2002 which has been split. In the part containing the data (back end I think its called) there are 3 existing tables which are clearly linked from the front end (forms queries etc.). If I now try to add another table in the back end it is not shown in the list when trying to create a link from the front end.
I'm running Access 2002 at work and trying to import a form that was created in Acrobat 7.0 and saved as a xml file. The structure and data option is selected, yet only the structure imports, no data.
In Access 2003 (which is what I have at home) I can get both structure and data. Does anyone know away around this in trying to import the file into Access 2002 or why I might be having that problem with one version and not the other?
I am trying to build a database for my share trading and am having trouble doing some calculations in a Report.
In the Detail section of the Report I do this calculation: =IIf([LVR]="0","0",((([Units]-([Margin Amount]/[Unit Price (o)]))*[Close Price (c)])/(1-[LVR]))+(([Margin Amount]/[Unit Price (o)])*([Close Price (c)]-[Unit Price (o)])/(1-[LVR])))
This calc is done on all my open trades and it returns the answer i want which looks like:
Margin Calculations
Open Trades
ASXCodeCurrent ValueMargin Available
FLT$5,500.00$18,333.33
SGN$3,700.00$3,200.00
AXN$13,200.00$33,000.00
CPU$9,250.00$17,821.67
AUN$15,600.000
Total Margin Available:$5.00
Inthe report footer i attempt to sum the answers this calculation returns using the Expresion: =Sum([Margin]) to get Total Margin Available.
Margin is the name of the field that contains the above calculation and when I try to veiw the report it prompts me to enter a parameter for Margin? I would have thought no parameter is required as all I am asking it to do is sum the numbers the calculation is churning out, however if i enter a value ie 1 Total Margin Available totals the number of records and multiplies it by the value i entered as you can see in the above example ($5.00).