Search results

I respectfully disagree completely and emphatically with ruralguy's link. The pro's of Lookups are well documented here and on other Access (or other relational dbs) sites, whereas each of the con's linked above are easy to avoid with good db design.

Don't store the hyphen. Create a query that contains all of your table's values, with a calculated field to add in the hyphen where appropriate. Then use the new field everywhere that you need the hypenated field to appear.

I put together a recursive design once for a power utility network outage tracker, where a device supplied none or more (1:M) devices, which in turn supplied none or more devices, etc, with no theoretical end. Each device had exactly one source ('Parent'), so I didn't need more than one table...

Are sure that you need to STORE all of this data in another table, or just be able to DISPLAY this data on one or more forms and reports? Data that NEVER changes should not be stored more than once. I suspect your product name and description are fixed w.r.t. the StockID, whereas the...

If you are still working on this, research 'crosstab queries'

I can think of a code-free 'brute force' way to do this for all patients, but you are going to need some 'cascading' queries! 1) Create a summary query that finds the newest (max) reading and oldest (min) reading, grouped by patient, that shows the [readingtime]. 2) Create a query that returns...

Assuming you have a proper date/time field to timestamp your reading called [ReadingTime], you can do this with 4 queries: SELECT TOP 10 {FIELDS} FROM {TABLE} ORDER BY [ReadingTime] gets the 10 'smallest' or oldest readings. SELECT TOP 10 {FIELDS} FROM {TABLE} ORDER BY [ReadingTime] DESC...

Presumably, your intended use of Tamil requires the use of one or more tamil fonts. Look at http://tamil.net/tscii/ (I found it on a Google search!). So, just change the font property of your tamil control(s) on your form(s) to use this font, and ensure that EVERY user has this font installed...

You need ampersands (&) to concatenate strings together, such as Like '"*"&[String Names]&"*"'

You may find it easier to take advantage of the user's network ID (rather than using CurrentUser()), and then have a 'rights lookup table' that allows code to enable rights (assuming you do all of the stuff described by the rest of this thread to lock down access. In a code module, add the...

It may be easier to keep your former ID and location fields for 'historical reference', and generate a NEW PK field (such as an autonumber) to use from now on. This way, you have simple, efficient, one-field joins and can still go back look at old paperwork, since your [OldPartNum] value is...

Is [start date] defined as a date/time field (as opposed to a text field with data that 'looks' like a date)? If so, then the Query Wizard should be able to automatically group by month for you. Once it is done, be sure to look at the query design grid to see how it was done. (The wizard...

That is more like what I would do. in the convention that I happen to follow, I would name the link table [LocationOwnerLink], but that is just a quibble. I am unsure why your [Owner]-[LocOwn] join is showing the way it is if you have enabled RI, as it should then show the 1:M symbols on the join.

Suggestion: Enable referential integrity (RI) on your relationships, to make the 'one' and 'many' side more clear. As a matter of general practice, the foreign keys (FKs) on the 'many' side of 1:M relationships need to point to the Primary Key (PK) on the 'one' side of the join. Do not make a...

There's a better way, if you have to do this sort of thing a lot. Create a SUMMARY query on your table, grouping your records by month, and then adding the appropriate field to COUNT. You'll get a nice output, with one record per month. I believe that the Query Wizard can be used to set up...

How about 'Sam'

OR, just change your edge values to 1401 and 2159!

In the query design grid, when you use the between ... and ... criterion option, it defaults to inclusive (>= AND <=) In Boolean, you are really saying: >= 1400 AND <= 2200 in a criterion row for [startdates] >= 1400 AND <= 2200 in a different criterion row for [enddates] By putting these on...

BTW, if you really have a field called [Date], you should change its name to [TheDate] or something, as 'Date' is also used for a function call, which can create REALLY bizarre behavior if you were to vba program in certain ways.

A few issues for you to mull (over and above the critical ones about doing lots of planning and a little research into understanding of how relational databases such as Access works. The previous posters were certainly correct that you can't treat this like just another kind of speadsheet)...