Search results

So would the table have brand in column 1 and then the sub brands in 2, 3, 4 etc. as nessescary?

I too am interested in doing this, My brands are not in their own table but rather just set up in the value list on the properties tab. How could I implement this? I'm not too worried about the secondary box updating if the first 1 is changed.

all right, i replaced the file above with a 2003 version.

here is a stripped down version, you'll notice all of the reports have the same fields and layout. I am trying to have just one report that chooses the fields from the appropriate table based on which form the "print label" button is being pressed from.

sorry, newb here. Can you help me with implementing this?

I have a print button on my form using the following code to print a single record report: Private Sub Command26_Click() Dim strDocName As String Dim strLinkCriteria As String DoCmd.RunCommand acCmdSaveRecord strDocName = "InventoryTagBusway" strLinkCriteria = "ID = Forms![BUSWAY]![ID]"...

Thanks So Much

try the newly attached database here: its going to print preview now but all the fields are blank?

i just tried it am i get nothing at all with this. no errors, no print, nothing.

I have searched and found countless threads for how to print a single record being being viewed on a form to report but none of them seem to be working for me, it still keeps printing ALL records. I have attached a simple sample database of what i'm working with, it has a table, a form, and the...

also, since every part has a "manufacturer" column, should i move that out of the attributes table and into table1?

Thanks Bob, I made the changes to the names and data type fields and also checked "enforce referential integrity" as you had in your sample db. what feature do i need to use to export the data to a flat like view that i need it in on occasion for viewing? also, If i made flat sheets of part #...

i thought that is what i have done, take a look.

so is this what i should end up with?

So might it be best to take my 10 or so individual tables and import them into this format suggested by boblarson? haven't looked at doing it yet, would it be difficult? also BobLrson, you didnt clarify your field decriptions that i asked about in the 3rd or 4th post down.

well if i can keep it to say about 10 tables (eg,. (circuit breakers,boxes, batteries,terminals, etc.) to decribe similar parts to avoid the blank fields created if i were to keep it all in one which might creat 50 to 60 columns vs. about 10 ea if they were individual tables? is this a bad...

my problem is that it is often nessesscary for us to sort a table of parts in various manners when trying to search for a part or maybe a part that is similar that can be used as a substitute and it is much eaier to do when all the data is layed out in front of you and you can just click column...

Bob, i see your design fundamentals for a normalized database, it just seems daunting for each new part number entry to indivually select the associated attributes and then value them every time. then on top of that without the part number being set as the key, it allows for duplicate entry of...

So in table one, the "PartDescription - Text" would bea short desc. like box, or circuit breaker? in table two the "PartID - Long Integer (foreign key from Parts Table)" would be the actual part number or the auto number next to it? for looking up parts by their decription would there just be...

I am confusing myself more and more as i read on normalization and queries and everything else. I am trying to create a database for parts that our company sells and am having trouble deciding how to lay out the tables. I figure I should use the part number for the primary key as it will not...