Search results

If you are still working on this... I would simply use an autonumber 1 to n for your actual [subjectPK] primary key that connects your data to the subject, and use a long integer FK in all of the related tables. Then you can use all of the typical Access techniques to build your db. HOWEVER...

You didn't describe how the letter prefix is chosen. Is it assigned at random? Is it one of their initials, etc? Do you go A001, B001, ..., Z001, A002, B002 etc? Does the user get to pick it? This will affect your 'best way'. BTW, this only gives you 26*1000=26000 possible combos. Will...

AFAIK, the spam bots often post to the first or top forum. So, I would suggest set up a structure like you have proposed, but add one at the top, such as "Testing: Do not post here" that can catch much of the spam. The downside is that this would be right at the top of the list, which is...

By the way, at the risk of hijacking this thread a bit, my own naming convention seems quite similar to yours, but with a difference: On the 'many' side of the relationship, I use the suffix 'FK' where you use ID. So in your example, the PK in the Employee table would be called [EmployeeID]...

I think I agree with Doc_Man on this. Everyone needs to follow a formal NAMING convention. Yours certainly has its merits, but there others that are good as well. However, the CONTENTS of the fields and the NAMES of the fields are two distinct things. The top structure of your .jpg can be...

What you will learn in engineering: * You can study hard and still fail * You can not study and pass * Multiple choice does not mean easy * There are no trains here * Six exams can be written in 4 days, but it hurts * You can skip all the classes, study for 15 minutes before the final...

Psychologically, a square patty looks 'larger' than a round one, for the same amount of meat. Also, having the corners of the patty poking out at you increases the impression that you are getting more meat.

Advantage FOR meaningful (MF) keys: (Assuming all of the previously-stated strenuous criteria for selecting a MF key are met) The resulting db structure should be easier to understand, particularly for people other than the original developer(s). This can be really handy if the db survives for...

In my opinion, a truely unique meaningful (MF) key might be better than a meaningless (ML) key, unless performance requirements dictate limiting the PK to an autonumber-sized entity. However, finding a truely-unique, under all possible foreseeable circumstances, MF can be difficult, and...

from http://en.wikipedia.org/wiki/Microsoft_Jet_Database_Engine

I buy WEINERS in a package of 10. I buy buns in packages of 8. On average, 7 of the WEINERS go into the buns to make hot dogs, and three of the WEINERS are eaten, sans bun, by my son who doesn't like the bun. I actually have EXTRA BUNS. Do you think that they sell packages of SEVEN buns?

Proposed argument FOR meaningless key: 4) Sometimes, it is impossible/difficult to find a meaningful key that is GUARANTEED to be unique. I have encountered several cases where an assumed-to-be-unique key turned out out to be non-unique when more data was merged/linked in from other sources...

1) Create a summary query that groups by the records that you have on your subform, and COUNTS them in a new field. 2) Copy this into another query (with a different name!) and add a 'where' option for 'completed=true' 3) Create another query that contains all of the relevant fields (or use the...

OP: Search this forum on 'surveys' as this topic has been discussed before. Rule of Thumb: If you ever find yourself wanting to add/average/count/std dev/etc with similar FIELDS in the SAME RECORD, there's a real strong possibility that your tables are not normalized.

What you have is a sample of a spreadsheet. If this is your Access table structure, then you are not normalized You should have a table structure like: RecordID (autonumber), to uniquely identify each record. {Optional, but strongly recommended} SampleID (integer) CriterionID (integer) Value...

http://www.access-programmers.co.uk/forums/showthread.php?t=105243

How do you kill a yellow elephant? Tell him dirty elephant jokes until he turns pink, then shoot him with a pink elephant gun.

As long as we're doing bad elephant jokes... How do you get four elephants in a little red mini? Two in the front, two in the back How can you tell if an elephants been in the fridge? There's a set of footprints in the butter How can you tell two elephants have been in the fridge...

Workaround: design a smaller (say half-sized) report, and scale it to 200% at the printer driver before you output or preselect your paper size, and select 'scaled to fit' on your printer settings.

ditto what Doc_Man said. Assuming (rather than FORCING) a sequence or order to be in a table can lead to DISASTER. In excel, add another column with a simple formula like (assuming your range starts at A1): D3: +iif(A3<>"",A3,A2) (and copy down as needed in D) and use column D rather...