If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Navigation buttons
I am creating a database with multiple fields, including a list box, text
boxes, and labels. When I test the form to add records, I can add one, then to add another, there are no navigational buttons to choose from and enter doesn't work to get to the next record. Can someone tell me what Property needs to be corrected and where to find it? -- Dorothy |
#2
|
|||
|
|||
Navigation buttons
The default Access behaviour is to add a new record when you navigate away
from it. So once you have updated your new record, you click on the |* icon again to bring up the next new record. -Dorian "Dorothy" wrote: I am creating a database with multiple fields, including a list box, text boxes, and labels. When I test the form to add records, I can add one, then to add another, there are no navigational buttons to choose from and enter doesn't work to get to the next record. Can someone tell me what Property needs to be corrected and where to find it? -- Dorothy |
#3
|
|||
|
|||
Navigation buttons
Yes, I realize that, but those navigational buttons are shaded and I can't
figure out how to unshade them. I thought it might have something to do with the properties to add records or data entry to yes, but that didn't help either. -- Dorothy "mscertified" wrote: The default Access behaviour is to add a new record when you navigate away from it. So once you have updated your new record, you click on the |* icon again to bring up the next new record. -Dorian "Dorothy" wrote: I am creating a database with multiple fields, including a list box, text boxes, and labels. When I test the form to add records, I can add one, then to add another, there are no navigational buttons to choose from and enter doesn't work to get to the next record. Can someone tell me what Property needs to be corrected and where to find it? -- Dorothy |
#4
|
|||
|
|||
Navigation buttons
look at the NavigationButtons property although if that is set to no, you
would not see the buttons they would not be grayed out. Also look at AllowAdditions property It sounds like you have filtered down to a single record and therefore there is no other record to navigate to. -Dorian "Dorothy" wrote: Yes, I realize that, but those navigational buttons are shaded and I can't figure out how to unshade them. I thought it might have something to do with the properties to add records or data entry to yes, but that didn't help either. -- Dorothy "mscertified" wrote: The default Access behaviour is to add a new record when you navigate away from it. So once you have updated your new record, you click on the |* icon again to bring up the next new record. -Dorian "Dorothy" wrote: I am creating a database with multiple fields, including a list box, text boxes, and labels. When I test the form to add records, I can add one, then to add another, there are no navigational buttons to choose from and enter doesn't work to get to the next record. Can someone tell me what Property needs to be corrected and where to find it? -- Dorothy |
#5
|
|||
|
|||
Navigation buttons
I won't be able to post again until Monday, but I'm just wondering if you
are referring to the built-in navigation buttons that appear at the very bottom of the form, or to custom buttons on the form itself. I think you mean the built-in ones, but I want to be clear on that. "Dorothy" wrote in message ... Yes, I realize that, but those navigational buttons are shaded and I can't figure out how to unshade them. I thought it might have something to do with the properties to add records or data entry to yes, but that didn't help either. -- Dorothy "mscertified" wrote: The default Access behaviour is to add a new record when you navigate away from it. So once you have updated your new record, you click on the |* icon again to bring up the next new record. -Dorian "Dorothy" wrote: I am creating a database with multiple fields, including a list box, text boxes, and labels. When I test the form to add records, I can add one, then to add another, there are no navigational buttons to choose from and enter doesn't work to get to the next record. Can someone tell me what Property needs to be corrected and where to find it? -- Dorothy |
#6
|
|||
|
|||
Navigation buttons
I mean the built in buttons on the form, that show up on the form and the
datsheet view. I have played with the AllowAdditions property and still only 2 navigational buttons show up. I just started this project, so, I've put in test information to make sure it works, and found when I go to add another record it won't let me. I will be back on Monday at work too, may take it home for the weekend, so if any one has any ideas, I'll keep checking. Thanks. -- Dorothy "BruceM" wrote: I won't be able to post again until Monday, but I'm just wondering if you are referring to the built-in navigation buttons that appear at the very bottom of the form, or to custom buttons on the form itself. I think you mean the built-in ones, but I want to be clear on that. "Dorothy" wrote in message ... Yes, I realize that, but those navigational buttons are shaded and I can't figure out how to unshade them. I thought it might have something to do with the properties to add records or data entry to yes, but that didn't help either. -- Dorothy "mscertified" wrote: The default Access behaviour is to add a new record when you navigate away from it. So once you have updated your new record, you click on the |* icon again to bring up the next new record. -Dorian "Dorothy" wrote: I am creating a database with multiple fields, including a list box, text boxes, and labels. When I test the form to add records, I can add one, then to add another, there are no navigational buttons to choose from and enter doesn't work to get to the next record. Can someone tell me what Property needs to be corrected and where to find it? -- Dorothy |
#7
|
|||
|
|||
Navigation buttons
Going back to your original post, you said that you are "creating a database
with multiple fields, including a list box, text boxes, and labels." Tables have fields, which are where data are stored. List boxes, text boxes, etc. are called controls. They appear on forms and reports. Is your form bound to a record source? Are your controls bound to fields in that record source? When you open the form in design view, click View Properties to check the Record Source. Click a control, then click View Properties to see its Control Source. The problem could be that your form has no record source. An unbound form will have the navigation buttons grayed out. There is no next record or previous record because there is no record at all. You said that you tested the form by adding data. Did the data get stored in a table? "Dorothy" wrote in message ... I mean the built in buttons on the form, that show up on the form and the datsheet view. I have played with the AllowAdditions property and still only 2 navigational buttons show up. I just started this project, so, I've put in test information to make sure it works, and found when I go to add another record it won't let me. I will be back on Monday at work too, may take it home for the weekend, so if any one has any ideas, I'll keep checking. Thanks. -- Dorothy "BruceM" wrote: I won't be able to post again until Monday, but I'm just wondering if you are referring to the built-in navigation buttons that appear at the very bottom of the form, or to custom buttons on the form itself. I think you mean the built-in ones, but I want to be clear on that. "Dorothy" wrote in message ... Yes, I realize that, but those navigational buttons are shaded and I can't figure out how to unshade them. I thought it might have something to do with the properties to add records or data entry to yes, but that didn't help either. -- Dorothy "mscertified" wrote: The default Access behaviour is to add a new record when you navigate away from it. So once you have updated your new record, you click on the |* icon again to bring up the next new record. -Dorian "Dorothy" wrote: I am creating a database with multiple fields, including a list box, text boxes, and labels. When I test the form to add records, I can add one, then to add another, there are no navigational buttons to choose from and enter doesn't work to get to the next record. Can someone tell me what Property needs to be corrected and where to find it? -- Dorothy |
#8
|
|||
|
|||
Navigation buttons
Hi! In answer to your questions: The form is not bound to any source,
either a control source or record source. Not even the list box, which only has a value list in it that I entered, but doesn't show up on the datasheet view, the other fields do, but the list box doesn't. So, I gather that I'm not saving anyting either, since I opened it from the weekend, and none of the previous data was there. Also, the titles on some of the fields in the datasheet view are different than the ones on the actual form. Should I start over, and make a table first, except, I did that, and when I went to create the form, the form created a new datasheet view, so then I had 2. Or do I just have to connect the form to the datasheet, and then I'll be able to change the titles of those other columns through table design, which I don't have access to at this time. -- Dorothy "BruceM" wrote: Going back to your original post, you said that you are "creating a database with multiple fields, including a list box, text boxes, and labels." Tables have fields, which are where data are stored. List boxes, text boxes, etc. are called controls. They appear on forms and reports. Is your form bound to a record source? Are your controls bound to fields in that record source? When you open the form in design view, click View Properties to check the Record Source. Click a control, then click View Properties to see its Control Source. The problem could be that your form has no record source. An unbound form will have the navigation buttons grayed out. There is no next record or previous record because there is no record at all. You said that you tested the form by adding data. Did the data get stored in a table? "Dorothy" wrote in message ... I mean the built in buttons on the form, that show up on the form and the datsheet view. I have played with the AllowAdditions property and still only 2 navigational buttons show up. I just started this project, so, I've put in test information to make sure it works, and found when I go to add another record it won't let me. I will be back on Monday at work too, may take it home for the weekend, so if any one has any ideas, I'll keep checking. Thanks. -- Dorothy "BruceM" wrote: I won't be able to post again until Monday, but I'm just wondering if you are referring to the built-in navigation buttons that appear at the very bottom of the form, or to custom buttons on the form itself. I think you mean the built-in ones, but I want to be clear on that. "Dorothy" wrote in message ... Yes, I realize that, but those navigational buttons are shaded and I can't figure out how to unshade them. I thought it might have something to do with the properties to add records or data entry to yes, but that didn't help either. -- Dorothy "mscertified" wrote: The default Access behaviour is to add a new record when you navigate away from it. So once you have updated your new record, you click on the |* icon again to bring up the next new record. -Dorian "Dorothy" wrote: I am creating a database with multiple fields, including a list box, text boxes, and labels. When I test the form to add records, I can add one, then to add another, there are no navigational buttons to choose from and enter doesn't work to get to the next record. Can someone tell me what Property needs to be corrected and where to find it? -- Dorothy |
#9
|
|||
|
|||
Navigation buttons
Just to clarify something a bit, a bound form may be bound to either a table
or a query. Tables contain fields. A personnel table may contain LastName, FirstName, Street, City, etc. Each one of those distinct pieces of information is contained in a field. A query is based on a table or tables, so a query also contains fields. After the form is bound to a table or query (the form's Record Source), individual controls such as text boxes may be bound to fields in that record source. Not all controls are bound. However, if the information that is entered into a control needs to be stored in a field in the form's underlying Record Source table or query, the control mut be bound to that field. A form may be bound to a record source, and a control to a control source. The two are different from each other. It sounds as if there is already a table. Are there records in that table? How did they get there? In answer to your specific questions, an Access database starts with tables and the relationships between them. Only after this structure is built may queries, forms, and reports be built. Additional comments inline. "Dorothy" wrote in message ... Hi! In answer to your questions: The form is not bound to any source, either a control source or record source. Not even the list box, which only has a value list in it that I entered, but doesn't show up on the datasheet view, the other fields do, but the list box doesn't. When you are speaking of the datasheet view, I assume you mean a table or query. If the intention of the list box is to select information that is to be stored in the table, then list box needs to be bound to a field in the form's record source. So, I gather that I'm not saving anyting either, since I opened it from the weekend, and none of the previous data was there. Correct, you are not saving anything, since the form is not bound to a record source. A table is the only place where data can be stored. Remember that if the record source is a query, you are still storing the data in a table, since the query is based on a table. Also, the titles on some of the fields in the datasheet view are different than the ones on the actual form. Irrelevant. The names of fields are of no consequence to what the user sees. You should use labels to identify things on the form. A label caption may be anything at all. Should I start over, and make a table first, except, I did that, and when I went to create the form, the form created a new datasheet view, so then I had 2. I don't know what you mean when you say the form created a new datasheet view. Yes, start with the table. The simplest way to create a form is with Autoform. Select a table in the database window. That is probably what you see when you open the database. In contains tabs for tables, queries, forms, etc. After selecting the table, click Insert Autoform from the menu bar. This will create a generic form based on the table. It will give you the basic idea of how a form relates to a table. After the form is created (give it a helpful name so that you can remember what it is later), switch to design view and look at its properties as described in a previous post. Do the same for the controls (text boxes). You can customize the autoform by, for instance, changing a text box to a list box. Or do I just have to connect the form to the datasheet, and then I'll be able to change the titles of those other columns through table design, which I don't have access to at this time. If by datasheet you mean the table or query, yes, you need to connect the form to that record source. If the tables have been designed, leave them alone. -- Dorothy "BruceM" wrote: Going back to your original post, you said that you are "creating a database with multiple fields, including a list box, text boxes, and labels." Tables have fields, which are where data are stored. List boxes, text boxes, etc. are called controls. They appear on forms and reports. Is your form bound to a record source? Are your controls bound to fields in that record source? When you open the form in design view, click View Properties to check the Record Source. Click a control, then click View Properties to see its Control Source. The problem could be that your form has no record source. An unbound form will have the navigation buttons grayed out. There is no next record or previous record because there is no record at all. You said that you tested the form by adding data. Did the data get stored in a table? "Dorothy" wrote in message ... I mean the built in buttons on the form, that show up on the form and the datsheet view. I have played with the AllowAdditions property and still only 2 navigational buttons show up. I just started this project, so, I've put in test information to make sure it works, and found when I go to add another record it won't let me. I will be back on Monday at work too, may take it home for the weekend, so if any one has any ideas, I'll keep checking. Thanks. -- Dorothy "BruceM" wrote: I won't be able to post again until Monday, but I'm just wondering if you are referring to the built-in navigation buttons that appear at the very bottom of the form, or to custom buttons on the form itself. I think you mean the built-in ones, but I want to be clear on that. "Dorothy" wrote in message ... Yes, I realize that, but those navigational buttons are shaded and I can't figure out how to unshade them. I thought it might have something to do with the properties to add records or data entry to yes, but that didn't help either. -- Dorothy "mscertified" wrote: The default Access behaviour is to add a new record when you navigate away from it. So once you have updated your new record, you click on the |* icon again to bring up the next new record. -Dorian "Dorothy" wrote: I am creating a database with multiple fields, including a list box, text boxes, and labels. When I test the form to add records, I can add one, then to add another, there are no navigational buttons to choose from and enter doesn't work to get to the next record. Can someone tell me what Property needs to be corrected and where to find it? -- Dorothy |
#10
|
|||
|
|||
Navigation buttons
That helps a bit. Thank you for your advice and information.
-- Dorothy "BruceM" wrote: Just to clarify something a bit, a bound form may be bound to either a table or a query. Tables contain fields. A personnel table may contain LastName, FirstName, Street, City, etc. Each one of those distinct pieces of information is contained in a field. A query is based on a table or tables, so a query also contains fields. After the form is bound to a table or query (the form's Record Source), individual controls such as text boxes may be bound to fields in that record source. Not all controls are bound. However, if the information that is entered into a control needs to be stored in a field in the form's underlying Record Source table or query, the control mut be bound to that field. A form may be bound to a record source, and a control to a control source. The two are different from each other. It sounds as if there is already a table. Are there records in that table? How did they get there? In answer to your specific questions, an Access database starts with tables and the relationships between them. Only after this structure is built may queries, forms, and reports be built. Additional comments inline. "Dorothy" wrote in message ... Hi! In answer to your questions: The form is not bound to any source, either a control source or record source. Not even the list box, which only has a value list in it that I entered, but doesn't show up on the datasheet view, the other fields do, but the list box doesn't. When you are speaking of the datasheet view, I assume you mean a table or query. If the intention of the list box is to select information that is to be stored in the table, then list box needs to be bound to a field in the form's record source. So, I gather that I'm not saving anyting either, since I opened it from the weekend, and none of the previous data was there. Correct, you are not saving anything, since the form is not bound to a record source. A table is the only place where data can be stored. Remember that if the record source is a query, you are still storing the data in a table, since the query is based on a table. Also, the titles on some of the fields in the datasheet view are different than the ones on the actual form. Irrelevant. The names of fields are of no consequence to what the user sees. You should use labels to identify things on the form. A label caption may be anything at all. Should I start over, and make a table first, except, I did that, and when I went to create the form, the form created a new datasheet view, so then I had 2. I don't know what you mean when you say the form created a new datasheet view. Yes, start with the table. The simplest way to create a form is with Autoform. Select a table in the database window. That is probably what you see when you open the database. In contains tabs for tables, queries, forms, etc. After selecting the table, click Insert Autoform from the menu bar. This will create a generic form based on the table. It will give you the basic idea of how a form relates to a table. After the form is created (give it a helpful name so that you can remember what it is later), switch to design view and look at its properties as described in a previous post. Do the same for the controls (text boxes). You can customize the autoform by, for instance, changing a text box to a list box. Or do I just have to connect the form to the datasheet, and then I'll be able to change the titles of those other columns through table design, which I don't have access to at this time. If by datasheet you mean the table or query, yes, you need to connect the form to that record source. If the tables have been designed, leave them alone. -- Dorothy "BruceM" wrote: Going back to your original post, you said that you are "creating a database with multiple fields, including a list box, text boxes, and labels." Tables have fields, which are where data are stored. List boxes, text boxes, etc. are called controls. They appear on forms and reports. Is your form bound to a record source? Are your controls bound to fields in that record source? When you open the form in design view, click View Properties to check the Record Source. Click a control, then click View Properties to see its Control Source. The problem could be that your form has no record source. An unbound form will have the navigation buttons grayed out. There is no next record or previous record because there is no record at all. You said that you tested the form by adding data. Did the data get stored in a table? "Dorothy" wrote in message ... I mean the built in buttons on the form, that show up on the form and the datsheet view. I have played with the AllowAdditions property and still only 2 navigational buttons show up. I just started this project, so, I've put in test information to make sure it works, and found when I go to add another record it won't let me. I will be back on Monday at work too, may take it home for the weekend, so if any one has any ideas, I'll keep checking. Thanks. -- Dorothy "BruceM" wrote: I won't be able to post again until Monday, but I'm just wondering if you are referring to the built-in navigation buttons that appear at the very bottom of the form, or to custom buttons on the form itself. I think you mean the built-in ones, but I want to be clear on that. "Dorothy" wrote in message ... Yes, I realize that, but those navigational buttons are shaded and I can't figure out how to unshade them. I thought it might have something to do with the properties to add records or data entry to yes, but that didn't help either. -- Dorothy "mscertified" wrote: The default Access behaviour is to add a new record when you navigate away from it. So once you have updated your new record, you click on the |* icon again to bring up the next new record. -Dorian "Dorothy" wrote: I am creating a database with multiple fields, including a list box, text boxes, and labels. When I test the form to add records, I can add one, then to add another, there are no navigational buttons to choose from and enter doesn't work to get to the next record. Can someone tell me what Property needs to be corrected and where to find it? -- Dorothy |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Navigation Buttons not working (HTML) | Mariusz K | General Discussion | 0 | October 18th, 2005 04:37 PM |
Customize Navigation Pane to allow Folder View ONLY - NO BUTTONS! | rkenchel | General Discussion | 2 | September 15th, 2005 06:56 AM |
Custom Navigation Buttons in Microsoft Access | K. Armstrong | General Discussion | 2 | August 4th, 2005 09:23 PM |
Navigation buttons | Sheldon | Using Forms | 1 | January 7th, 2005 09:28 PM |
Report navigation buttons disappear | Amir | Setting Up & Running Reports | 0 | August 14th, 2004 06:33 PM |