I am designing a form for users to write letters in which they give “reasons” for denying a particular service. It is a State-required form letter and there are 7 “reasons” to deny. The user usually chooses just one “reason” and then types in (free-style) the text for the specific rationale (Memo field). Sometimes, however, they need to choose more than one “reason” so I have to design the table to accommodate up to 7 “reasons”.
For the underlying table I could create 7 fields, one for each reason, but this seems like a very inefficient use of disk space as most records would always have 6 blank fields.
Anyone have an idea for a table(s) design? I know this calls for some kind of dynamic procedure or pehaps a separate table to store the “reasons” but I am stuck and my brain is froze.
Thanks in advance for any and all replies!!
I'm hoping someone can help me with this one. I have a database that tracks seminars and registrations. I need to revise it as they want to allow an individual to add in up to 10 more additional people on their registration.
The simple way would be to do the following (you'll see my 10 additional fields in here), but I don't think this is the 'RIGHT' way:
Tbl_New_Registrations Registration_Number - Autonumber - PK Seminar_Name - Lookup (goes to Tbl_Seminars) First_Name - Text Last_Name - Text Business_Name - Text Years_in_Business - Number Address - Text City - Text State - Text Zip - Text Phone - Text E_Mail - Text Questions - Memo Additional_Registrant1 - Text Additional_Registrant2 - Text Additional_Registrant3 - Text Additional_Registrant4 - Text Additional_Registrant5 - Text Additional_Registrant6 - Text Additional_Registrant7 - Text Additional_Registrant8 - Text Additional_Registrant9 - Text Additional_Registrant10 - Text
What I 'think' is required is an Additional_Registrants table, but I'm not sure how to do this so that when someone fills out a registration form, the 10 additional registrants go into this table and the database knows that these 10 belong to record X and so forth.
I am just querying a single table, no relationship involved with another table. As you can see form the attached jpeg, the ZIP field in some cases is empty. I would run a search using Is NULL but the field is NOT numerical. It's a long story but I had to make this field a TEXT field. Basically, what statement do I have to insert in the criteria field to just pull up the EMPTY ZIP fields?
My boss asked me to do something today that stumped me. He wanted me to make a query, where when you're selecting the parameters you could chose whether or not you wanted certain fields to be visible.
On top of that I need to be able to chose whether I want it to be shown on screen in a query, printed as a report, or exported to excel. This is what makes it tricky. I could easily do a bunch of If...then statements to generate the SQL query and only show the fields necessary, however the report and the query view both have the fields on them in design view. If I cut the fields out of the query at runtime, then I get the nasty "Input parameter" popup box.
So I've been bashing my head off the keyboard trying to figure out how I'm going to do this. One other theory I tried to put into use was having them left on the form/report, but if the checkboxes were not selected then it would set them to visible = false at runtime. Sounds good in theory, however Access decided to ignore this block of code and just show the fields regardless of what I told it to do.
So if anyone could provide me with some insight or suggestions, I would certainly appreciate it.
Find the link by tacking on the following to this site's primary [URL] .....
It was, essentially, a type-and-show-as-you-go search functionality for an Access Form. It works great, except that I'm experiencing intermittent slowness when using the form. As I type, the characters appear very slowly and experience a significant lag time.
I only have about 70 records so far, so I'm pretty sure the slowness is not being caused by an overabundance of data. At other times, it goes super fast without any lag.
I'm a BA so i'm converting my excel issues list into a database with a front end where i can create new issue records this uses a form that sits on top of the issues_table.
Howver, i have created a table called Projects and a table called Test_Plans
Each issue is logged against a project and a test plan. Lets say ProjectA has TestPlan1 and ProjectB has Testplan2.
On my issues form, i can select ProjectA in the project field.
In the Testplan field i can select EITHER TestPlan1 or Testplan2
Testplan1 is the only valid entry.
How do i
a) Once I have selected ProjectA in the Project field only display Testplan1 in the Testplan field?
or
b) If the user tries to enter testplan2 for it to error?
I've tried creating a query and linking the controlsource field to it but it doesn't like that!
I have a form that shows a list of all of my records in my database. I want to be able to click a button called "Report" and have that print a report that has all the records I have filtered on my form. I have a report in the format that i want it in, however, currently it prints every record and not just what is shown on my form. (The form is dynamic and I want the Report to be dynamically based on the form) HELP PLEASE!
I think I have the title right on my post. I have attached my db so my I am explaining maybe easier to understand. If you open the db and click Find and enter "Simpson", next click Select. For the "Schedule / Attendance" section I have created a table that will capture the 8 textboxes plus the SO ID of person, in this example Homer. But my problem is, say on May 18th he completes the Core 1 section, but don't complete the Core 2 until May 20th. I only want one record in the tblsch_att for Homer, but I don't know how I can search the table and find the entry from the 18th and Added the 20th to the corresponding record in the table. Furthermore, the only want I can get a record added to the tblsch_att table, is that I have to fill in all textboxes, but I intended to only to have Core1 done one day, Core2 the next day and so on. Make sense!
Any help on what function can complete this would be great.
I have a table and a form that I designed. Now I need to copy all the fields and the design of the form I just created and give it another name so my partner can use the same design and fields, but put in his own information. Is it possible to copy just the design and the fields. If so, how do I do that? Thanks.
Right now I have a subform with a combobox that pulls it's data from a table. I want the user to either select an existing item or type in a new item and have a macro create the new table row. What I have right now works in the sense that it prompts the user if they want to creat a new item and the new item is created (and I can see it in the combobox list), but I'm still getting an error saying that the item does not exist in the table forcing the user to manually select the newly created list item they just typed in.
Code: Private Sub MaterialCostCode_NotInList(NewData As String, Response As Integer) Dim rst As DAO.Recordset 'Update value list with user input. On Error GoTo ErrHandler Dim bytUpdate As Byte
[Code] ....
It appears that the new item doesn't always show up automatically and requires the form to be refreshed, so now I need to figure out how to get it to consistently appear right away without a refresh.
I have a query based on a query, when I added a new field to the base query, this field did not appear in the list of fields in the design definition when I try and add to the upper query. It just shows the original fields only.
Same thing happened in a field on a report - I had to delete the field and create it again...
I got a form called "Make quote". In this form a user can select a product from a line of fields. This "line" contains: article code, product, price and quantity the customer requests.
Each single quote can contain a very different amount of products. Some quotes just have 1 product, other quotes have 25 products.
I'm looking for a way to let the user add as many "lines" as necessary for the quote. BUT I don't want him to need to go into design view.
I'm thinking of maybe adding a button to the form which does this, but I'm not sure how.
I'm getting back into Access after retiring and about 10 years of isolation (from Access). I have 2010 version and know that one should avoid duplicate entries and a way to do this is make those fields unique key fields. I have a Customers table and have bounced back between CusID (AutoNumber) and Compound Keys (CusFName and CusLName) as the key fields. The compound keys prevent duplicates but become very hard to work with later in code and expressions. The CusID is preferable from that standpoint, but can't prevent inadvertent entry of duplicate names.
In the Lesson tutorial shown above I am clicking on tools and adding existing fields. I get a lot of output label and text box pairs for each field that I add.
However, they are all on right below the other. That is no problem just move them. No way.
Whenever, I move it a label and test box for say Order Status, I get ... nothing. It stays where it is.
They (label and text box) do not move together. So how do I get them to move together.
I am designing a database for my organisation. I have done most of it but am stuck on this. Ideally I would like to have a check box (in a table) that when checked a load of data is carried across from that record to a record in another table.
Given that I can't and don;t want to use VB is there anyway that this can be done easily?
This only shows the flow if the main category is "Floors", sub category "Joist", and then the choices under subcategory "Joist". There will be others for the other categories, subcategories, and choices.
Can someone help me or steer me in the right direction in setting up the database table/tables to accomplish this. Oh and BTW, there will be prices attached to each "Choice" under the subcategories.
I hope that this makes sense... any help would be much appreciated.
if i had a table with products and i want to keep a record of what has been chaged or added to this product, whilst keeping the old records how could i set it up in a databse?
the excel spread sheet looks like this
product commments
1 chnged this and that 20/08 1 modifyed component 21/08
It's a simple question really. I'm currently learning databases and am doing a project, just to show that i understand everthing i've learnt so far. I have to produce a small database.
There's nothing difficult about the project, and its a very basic database, but i was just hoping to ask a small question.
I'm producing a DVD database, to hold details on a collection. My main table holds the majority of the fields, as follows;
The problem came with boxsets. Originally i was just going to have boxsets as one entry, but some contain a few dvd's, each with different certification, etc, and i wouldn't be able to record running length, director, etc. So i added a ysnBoxset field (just to record whether a dvd was part of a boxset or not) and then made a new table with
lngDVD_ID strBoxsetName
So now i can record which are part of a boxset, and the name of the boxset they belong to. But.. then i got to the problem of Purchase Price. Obviously i cannot record an individual purchase price for those which belong to a boxset, and i want to be able to record the price of the boxset.
So my question is... is it acceptable to add a curBoxsetPrice field to tblBoxsets, which would allow me to store the price... and then just leave curPurchasePrice as £0.00 for those dvd's in a boxset??? Or is there a better way of doing it? (I know there is, but i'm a novice :( )
Thanks for any help you can give, sorry for the lengthy explanation! :rolleyes:
Within my db I have a table, tblProjects which currently has 36 fields. Each project will have a fixed set of 12 tasks, each having a begin and end date as well as a yes/no "completed" field. This would add another 36 fields to tblProjects.
Instead, I have created a new table tblTasks which has these 36 fields along with a PK(TaskID) and FK(ProjectID) and is related to tblProjects. I believe tblProjects is already normalized properly with relationships to tblCompanies and tblContacts as well.
I'm not sure if this was neccessary, or should I have just added the task fields to tblProjects. What, if anything, are the advantages of one way over the other? I'll be upsizing to SQL Server, does that make a difference?
Bit of a long one but I require some advise if people can supply it.
I've started creating a DB that is now getting out of hand due to me being inexperienced. The things I want to do now are getting way to complicated. From reading various posts I know that this is all being caused by my database design and while the DB is still young I'm go back to square one. I want your advice on this if you can to ensure 3 weeks from know I'm again not chasing up weird bits of VB code to make it all work.
I basically have a lot of information to hold that interconnects with each other. I'm making up a role profile DB (so we can assign define access rights to a computer system) I have lots of info to collate but the basic stuff is.
Staff Records (Name, business area & ID) Applications (What computer applications do staff require) Shared Drives (What access to shared drives and folders do they need) Shared Mailboxes (what access to shared mailboxes) Roles (users will be assigned roles to suit their requirements)
Basically what I have at the moment is below.
Roles Role ID Role Name and about 15 other fields that dont really matter for this
Applications Application ID Application
Shared Drives Shared Drive ID Shared Drive
Shared Mailbox Mailbox ID Mailbox
Each role will only have a select number of applications, mailboxes and drives from the overall list. so role 1 may give access to 2 of the 10 applications, 1 out of 5 shared drives and 3 out of 4 mailboxes. Role 2 on the other hand may need 9 out of the 10 applications, 1 out of the 5 shared drives and 1 out of 4 of the shared mailboxes.
I just don't understand how I can create a form from these tables that would display all the different roles with their respective apps, mailboxes and drives they would need.
any advice you can give to help whould be appreciated.
I am designing a db for our Law office. I want to have tables for different types of Civil Cases-ie Divorces, Deeds, Contracts, Personal Injury, Auto Accident, Slip and Fall, Product Liability, etc. The divorce, Deeds, tables are easy but I am having difficulty deciding on the personal injury tables. Heres my dilemna. Can I get away with one or two Personal Injury tables even though there will be blank data fields. For example, I will need a field for the name of the product in a Producrs Liability field. This field will be blank in all other Personal Injury Cases. I know the rule is you don't do that but my alternative is 15-20 tables for every concievable Personal Injury Case- Auto Accidents, Slip and Falls, Fraud, Prouduct Liability, Accounting, Attorney, Dental and Medical Malpractice, etc. This is in addition to other civil case tables, criminal case tables and federal case tables. Anyone have a suggestion?
I am not sure if which I should be using as the main entity for my tables. I am creating a database for hourly information on individual employees. Each employee will have the same types of hours to keep track of (weekly, bi-weekly, monthly etc) I naturally thought to treat each employee as the databases own entity and created fields for each type of hours but hit some trouble when trying to pull queries to compare each employees hourly information against each other to see who is being efficient or not. Each employee has the same exact fields but with just different numbers. We track each type of hour by week (Field One: Week 36, Field Two: Aug 28-Sep 03)This is the first time I am creating a database from scratch. All advice greatly appreciated and TIA :confused:
I have a table within a database and i was wondering whether or not i should split the table into 2 seperate tables.
The layout of the existing table is to record quotation information ie product codes, cost price, sell price, delivery dates available etc and it also contains fields that allow the user to state if the quote has been authorised or declined, when it was authorised and a number of options to explain the reason the quote wasn't accepted.
QuotationID - Primary Key EmployeeID - Foreign Key CustomerID - Foreign Key EnquiryID - Foreign Key ProductCode Quantity CostPrice SellPrice DeliveryDateAvailable Notes Authorised - Yes/No field Type DateAuthorised Declined - Yes/No field Type ReasonDeclined LostPrice - Yes/No field Type LostStock - Yes/No field Type LostDelivery - Yes/No field Type LostCustomerClient - Yes/No field Type LostNoFeedback - Yes/No field Type
above is the layout of the table, does anyone think that it might be a good idea to split this table into two tables, one table to record the quote information and another to hold the authorisation or decline information??????
