However, what do I have to do to programatically revert from my current version of Access to a previous version? Is there a shell option similar to the /CONVERT choice? It would be nice if it was as simple as /REVERT
I am trying to open a MS Access Database which was made in MS Access 1997 or MS Access 2000, at the moment i am using MS Access 2010, i cannot open the database or link the tables.i do not have MS Access 2000 anymore.
I'm having trouble reversing my query from read only. I set the query to read only at first and then decided to reverse this process. However, when i switched back to rewritable mode, the query still dosen't let me edit, add or update data.
In my form, when users check check boxes, then move onto the next form, the check boxes are still checked (and therefore screws with the functionality of some objects)
I've been trying to use defaultvalue, and trying to find a procedure I can implement the function on, but to no avail.
My table has a yes/no field and about 10 records. I have created a form for the user to select which of the records he wishes to use - the records are displayed in a continuous form with a check box for the yes/no field. The user is to select one record by checking the check box in the record.
I know this should be obvious, but I can't see it. How can I make it so the user can only select one of the records (when he clicks on one, that one is yes and the others revert to no?
I have a list of dates of births in a table, but the way they are always imported (from some piece of crappy software somewhere) is in the format of: 01.01.2005 (using full stops).
Access doesn't like this, and insists on slashes, or dashes. Now, if I do a find/replace, it works perfectly, just replacing all the full stops with slashes. However, I want to do this quite regularly...any ideas how to do it programatically in VBA?
Is it possible to unlink and link to tables in a back end using VBA in the front end?
I need to do this or something similar because when I send updates of the front end out I may have added an extra table and thus want to be able to get the user to run an update module to link any new tables.
I know you can manually delete table relationships in an .mdb, but I was wondering: Can you programatically delete table relationships? If it is possible, how would it be done?
I have a form that I am populating a ComboBox via a Query. It works but sometimes it flakes out and does not populate the box.
What I want to do is run this through code.
I am a bit stuck. I think that I need to set the recordset, Create a SQL query, Run the query and push the results to the ComboBox. Think this should be on the Click event of the combobox.
Dont really know where to get started.
Does anyone have a rough example of: 1. Getting the recordset 2. A general SQL query (how to run it) 3. How to push the results to the ComboBox
I could set the Combobox.Value to one of the values in the combo box and combo box displays that value. But when I try to use Combobox.Value subsequently it does not have any value. I noticed that the value property is populated only when the combox box item is manually selected(highlighted).
I have a subfom that displays perfectly in datsheet view.
One of the columns changes its contents depending on a value. i.e. a list of units or a list of costs. I change the data using a Recordset update.
When in the Main Form I am trying to change the column label that appears in the SubForm header above the column, to either 'Units' or 'Cost, to match the data.
I am strugging to find the correct syntax, can anyone help?
A have a query that selects a multivalue field. The query forms the record source for a subform. The text values in the multivalue field are displayed in the query, but when I save this and view the data in the subform datasheet view the values revert to the primary key values. They are 1,2,3,4 instead of the text values
Are there any issues with converting an older 97 database to 2003? Is it a straight conversion, or will there be differences that affect the way the database will run if converted? I've read somewhere that it is possible to use the newer version to open the database w/o converting it. It seems silly to have to install 97 on a new computer in order to view the db.
I just created a calendar pop-up for data entry in Access Version 2002 and it does not work with Access 2003. Any help from anybody would be appreciated!
An application that I made was created in Access 2000 as I was told that all users had at least this or newer. Of course a user with 97 popped up. Instead of having them purchase 2000 or newer I converted my app to 97 version. I expected troubles with references. So far this has only been a phone conversation and I plan on going there later today. The user says hitting alt/F11 does nothing... no code window comes up. I had her look through the menus for the code window but she says there is nothing there. She is getting runtime 3433 (she thinks) and unrecognized database format when trying to open a form. The database did open when holding the shift key though.
Before I go there, how do I open the code window for 97? Any other suggestions? I bet this is a reference thing but there may be a problem with their access install too. There are 2 users at this location with the same issues... at least it sounds like it.
I have a database which is use at busy times to run the delivery side of our Floristry business. The orders are entered,assigned to a delivery area, address labels printed. When it comes to delivery day orders are selected from the list ticked off then printed a make a list for the driver.
It was built using Access 97 when it first came out. Since then the software was upgraded to Access 2000 many mods have been made each year to improve the performance and the number of things it can do. It now has about 15 tables and a lot of queries. Not being an expert with Access a lot of the design has been on a trial and error basis. Put it another way the main form has many hidden fields to make things work behind the scenes. But it does most of what I want it to. I have now go to the point where the main query is saying that I can't add any more features because I have to many fields in it.
So the time has come to look at re building it for a number of reasons.
1. It is a stand alone database on one Pc.......... I would like to have it on a network to 3 or 4 Pc's around the shop. 2. Some of it needs to be redesigned to take out my ( it might not be the way a designer would it but it does work) type bits. 3 I would like to be able to use the system for all orders received on a day to day basis. So it will need to be used by other people.
My question today is Should I be looking to rebuilt it using Access 2003 + the extra software so that i can run it on more than one PC.
Or would it be better to wait few months till Acess 2007 comes out and start from scratch.
I've got an VB app that uses an Access db that sits on a sever. The owner of the app has no Access installled on site. The prior consultant created the app and used MS Access.
Is there a way for me to determne what version of Access this db was created in?
My boss get this message when open a form in his pc "Your Microsoft Office Access database or project contains a missing or broken reference to the file 'pdx.ocx' version 1.3"
Unfortunattely this message didn't appear in my pc :) . I make a small program to open a pdf file from access.
I am trying to determine what version of Access is being used from a file that I obtained from a user. Everything I clicked on does not say what version of Access is being used. The extension name of the file is .MDB. The original version of the file I am accessing was created in 2001. Thus would you tell me how to verify what version of Access I am working with?
I know its possible to have 2 different versions of Access installed, and that you have to uninstall then start in with the earliest version. BUT can I have 3 different versions? I think it should be no problem but thought I would ask first. I am looking at 97, 2000, and 2003. Plan is to do just Access 97, 2000, and then the full office install of 2003.
