I currently have an Access 2000 database which works just fine, but when I come to open it with Access2002 the relationship table is damaged.. All the links have gone and if I try to add some and then save it in 2002, they are gone when opened again !
I have tried exporting all the tables and queries in the 2000 database to a clean 200 database and created the relationship table again, but when it is opened in 2002 the same thing happens!
If someone can enlighten me as to where I am going wrong I would be most grateful.
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 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 am opening and closing a series of Excel 2000 Workbooks using Access 2000 VBA and want this sequence to be able to complete without any human intervention.
However, there are 2 instances when this stops and waits for a human option to be selected:
1. When the spreadsheet is password protected 2. When the spreadsheet has automatic links I get the message:
"The Workbook you opened contains automatic links to information in another workbook. Do you want to update this workbook with changes made to the other workbook?"
How can I code it so that in situation 1 it skips this file and in situation 2 it automatically defaults to do not update?
If I have a report in MS Access 2000 generated based on the criteria selected of a project with work order "9999" with the labor costs, materials costs and the Totals of each crew1, crew2,... and I would like to have those expenditures populated in corresponding cel in Excel for each crew, HOW would I do it?
To think it out loud, could I create a button on a form, so when I select the criteria for the work order, and when I click the button, it should refresh/update the Exel file with the new data...?? How do I write VBA code for that...?
I have recently been doing a conversion for my boss for a access 2000 database (both front and backend) to a MSSQL backend.
I finished the conversion today (as quite a lot of the code / queries ran slow due to access running the queries locally rather than on the server). And tested it on my and my boss's machine with no problems so he gave the go ahead to update everybody to our new mssql 2000 backend with the modified frontend.
This is when the problems started; We had two different sets of forms for accessing one of our databases systems - the log system, one is the original dynaset based form, and the other is a newer set which uses snapshot views and preforms updates via queries. Nobody uses the old dyanset system apart from my boss and one of the administrative team as they have things on that window which they need to see. About 30 minutes into the release of the new database the system frooze up on my bosses computer and nobody could create a new log (the server was timing out). I assumed this had something to do with the old dynaset's creating locks on the table.
I offlined the database and kicked everybody out of the front end, turned it on again and tied again, this time banning everybody from the dynaset system. Within 10 minutes another computer frooze up, again with a timeout on the insert query. I discovered that after you had added a new log to the database it would timeout on all subquent additions (something it hadn't done during testing) . Further investigatiion showed it was the snapshot list window causing the error, so coded the add log window to close the list before preforming the insert query and then reopen it afterwards. This allowed my machine to make multible additions without flaw. So I released a new client to everybody. 15 minutes later it was timing out again, but this time there you could not even make one new record.
I checked for locks on the table though the server management table and couldn't find any for the Log table. I have restarted the SQL server box and with no avil. So I reverted our backend to the access mdb file and told people to use the old client.
I am at a complete lose to why this is happening, if anybody has had any expericences like this or knows the cause please tell me.
Some information on the database in question.
It was made as an access 2 database all intergrated into one file, then it was seperated into two files (frontend and backend). Upgraded to Access 97, then to 2000 before this final update to MSSQL 2000.
The log system has two main tables. The first is the log title / info table which links (one to many) to a log entry table. This problem only occurs on the main log table and does not appear to be reoccurring anywhere else within the database. The main log table has just under 18,000 rows in it.
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 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?
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'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.
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.
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 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).
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.
Hi! I have constructed a database in Aceess 2002 that four persons or more are going to work with. The users have there own computers in the same network. And they are going to work in the database at the same time the database is placed on a shared drive in the network. They must have the possibility to work in the same bookingformular. Is there something that I have to think about so that everything works allright? I mean in the multiuser environment. I had a lot of problems when rhe same people worked with an Access 97 database, But I hope that Access 2002 is better for multiusers. Is that correct?
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.
