I am teaching a group of students how to make a simple database (its a very short course, just 3 x 2hr sessions). One of them has indicated that she sufferes from dyslexia and that this is making it difficult for her to populate the database correctly.
When she types columns of data in Excel, once she has input each entry correctly once, the autocomplete feature helps her with duplicates of the same entry (e.g. placenames).
I cannot find how to turn on autocomplete in Access 2003. Am I missing the obvious? Is it possible? If so where is the setting hidden?
I realise that the field type could be changed to "LookUp", but this would complicate the setting up of the database and would require all possible entries in that field to be pre-defined.
I need it keeping simple as the course is so short, the student will be on her own with it in just a couple of weeks.
I hope this isn't too stupid of a question :o but I've been trying to find a way to activate some kind of autocomplete function to help while entering data in a table and couldn't find it. So if for example, in a field in the table, I write data multiple times, access could autocomplete the words already seen, the way it's done when a field has the look-up option...Was wondering if there's a way for that..
Is there a feature in Access similar to Excel or Explorer where if you start complete a field with a word/phrase you have used before in the same field, it will suggest it? If not, can it be easily created?
Ihave a simpel database that records customers details. I have a form that lets me enter dockets recording deliveries by my customers. To simplify data entry is there anyway that I can enter a customers name in the form field and have it autocomplete if something similar exists (Like excel). A Drop down list would be too long if each customer was a new or how can I add a new name to a drop downlist withoput exiting the form???????
Are there any way to insert autocomplete in forms like how the internet explorer works ? In other words, when i type a few letters , the whole string of word will come out.
I'm not sure what you call it but I call it auto-complete; the functionality that gives you a list of methods/commands when you are typing something like Me.Forms. When you type the Me. after the . it will bring up a list for you to see what you can do from there. That works fine for me but when I do the following: "CoCmd." the list will popup for a brief moment (much less than half of a second) which does not let me view the possible methods. Is this normal? If not does anybody have any idea how I might be able to fix it short of reinstalling MS Office (that is NOT an option). Thanks, Aaron
I wasn't sure if it should go in this section or the VB section. I apologize if it is in the wrong section.
I am looking for a way to autocomplete in a unbound text, but I did not find any answer. So I am using this code that I used before in excel, but it doesn't work in Access.
Code: The purpose is just to copy the last name of member to last name of spouse if the first 2 characters matches.
Code: If abort Then abort = False: Exit Sub With Form_frm_proto If Nz(.lblSLastName) = Left(Nz(.lblLastName) & Chr(5) & Chr(5), 2) Then
I have an access form which 1 person updates daily, but the task after that is split between 2 users. I have got most of the form data automated with a combo box from a supporting table.
But I now want to automate a username & date, but based on a % and set of conditions.
(At the moment I go in at the end of the week and manually put those 2 usernames next to the new work thats been logged)
I'll try and explain:
user 1... gets 60% of the work user 2... gets 40% of the work
At the end of that day, when the form is completed with say 100 new records, I want to then run a query, macro (or anythying else that would do it automatically), to assign those usernames 'user1' to 60 of those 100 records... and 'user2' to 40 of the records. and also give it todays date.
I have create some forms which have some common fields, I have built relationships between them as well and I want to autocomplete the records in the fields with the relationships. For example I have a form with the client's details and I have install a Macro so that when I have complete the form with the new clients details and click on the Macro to automatically open the form with the clients order where this form has the clients ID and Name which are common with the fields in the Client's form. What I am trying to do is to autocomplete the common fields when I click the Macros to open the Order list.
I am making a library database which would be used in a school. I need to make a form which allows me to type in the persons id number then the persons profile will come up automatically then underneath there will be the persons book loans in a subform which i dont know how to do ...
So the top bit will have the persons details like personid, surname, first name, tutor group and then below there would b a subform with fields in from two different tables like from the book table there will be author surname, author firstname, bookname then from the loan table there will be the date the book was loaned field
The subform would also have to let me edit it so that i can add new loans or remove loans which i also dont know how to do but i was thinking if i had to add new records of the book would the subform have to autocomplete too? to save time typing all the details of the book
so so far i have made the tables added some test data and made relationships between the tables
a person can have many loans a book can have one loan
I think there is something to do with queries to make this whole thing work but I am totally lost what i have to do, I've been reading some forum posts which are similar about autocomplete forms which i have done but it wont work when i do it with the problem I have.
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.
