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
|
|||
|
|||
Tabbed Control Form
I have a database that I'm looking to provide a tidy front-end to.
Previously, the data was stored in Excel but this became unmanageable as it provided little reporting and data integrity was a real issue. As a part time task at work, I volunteered to migrate the "register" from XL to Access and that part has been done. In addition, all the reporting required has been built. Now the problem: the original table (one entry per 'work request') had some 70 - 80 columns and so a single page form was never going to be workable. after some research (I'm almost learning much of this as I go) I found the tab control and decided to build a new form based on that. All fine until I tried to edit - told that the record is uneditable. some research suggested that I could apply changes to the recordset property (which I did) and this did make things editable but it seems that the data no longer appears within the form. Hence, my question: can I make the data editable? The form data is based upon a query but I've checked and it's all one to one relationships which is something else that I think can cause the data to become uneditable. any assistance or ideas greatly appreciated. |
#2
|
|||
|
|||
"atropus32" wrote in message
... I have a database that I'm looking to provide a tidy front-end to. Previously, the data was stored in Excel but this became unmanageable as it provided little reporting and data integrity was a real issue. As a part time task at work, I volunteered to migrate the "register" from XL to Access and that part has been done. In addition, all the reporting required has been built. Now the problem: the original table (one entry per 'work request') had some 70 - 80 columns and so a single page form was never going to be workable. after some research (I'm almost learning much of this as I go) I found the tab control and decided to build a new form based on that. All fine until I tried to edit - told that the record is uneditable. some research suggested that I could apply changes to the recordset property (which I did) and this did make things editable but it seems that the data no longer appears within the form. Hence, my question: can I make the data editable? The form data is based upon a query but I've checked and it's all one to one relationships which is something else that I think can cause the data to become uneditable. any assistance or ideas greatly appreciated. If I understand you correctly, you can now enter data on the form, but no records are displayed. In which case, you probably want to set the form's Data Entry property to No. It's got nothing to do with the tab control. |
#3
|
|||
|
|||
On Fri, 14 Jan 2005 21:59:01 -0800, atropus32
wrote: I have a database that I'm looking to provide a tidy front-end to. Previously, the data was stored in Excel but this became unmanageable as it provided little reporting and data integrity was a real issue. As a part time task at work, I volunteered to migrate the "register" from XL to Access and that part has been done. In addition, all the reporting required has been built. Well... Excel is a spreadsheet, the best of the breed. Access is a relational database interface program. THEY ARE DIFFERENT. A good spreadsheet will very likely be a poorly normalized database! Now the problem: the original table (one entry per 'work request') had some 70 - 80 columns and so a single page form was never going to be workable. after some research (I'm almost learning much of this as I go) I found the tab control and decided to build a new form based on that. That may not be the best solution. I would strongly suggest that you should step back two paces and look at the table design. 70 fields is far less than the 255 field limit of a table - BUT it's still an EXTREMELY wide table; I've needed as many as 60 fields in a table, but 30 is still about as wide as I would ever want to get! All fine until I tried to edit - told that the record is uneditable. some research suggested that I could apply changes to the recordset property (which I did) and this did make things editable but it seems that the data no longer appears within the form. Hence, my question: can I make the data editable? The form data is based upon a query but I've checked and it's all one to one relationships which is something else that I think can cause the data to become uneditable. any assistance or ideas greatly appreciated. One to one relationhships are VERY RARE. If you're not familiar with the terms "Subclassing" or "Field level security", then it is likely that you are splitting up your spreadsheet incorrectly! What are your tables? Why are they one-to-one? In any case, rather than a massive Query reproducing the spreadsheet look, consider using a Form (for the "master" table) with Subforms (for the related tables). This will solve your updatability problems and very likely provide a better user interface as well. John W. Vinson[MVP] |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Strange stLinkCriteria behaviour on command button | Anthony Dowd | Using Forms | 3 | August 21st, 2004 03:01 AM |
dlookup | miaplacidus | Using Forms | 9 | August 5th, 2004 09:16 PM |
Access Calendar | lost | General Discussion | 2 | July 7th, 2004 04:58 AM |
How to assign value to a report control? | Peter | General Discussion | 3 | June 29th, 2004 11:17 AM |
Recordset in subform based on field in parent form | Lyn | General Discussion | 15 | June 14th, 2004 03:10 PM |