Recent content by SirTECH

Sorry for delaying getting back to you. The family pet passed away yesterday. Anyway, I greatly appreciate the detailed and useful reponse. I had a categories table similar to the one you suggested, but didn't have a measures reference table (and btw the term measures does make so much more...

The measures are all the same datatype (text), for each measure is also a rating (number).

The data is an analysis on an item. The item is analysed based on 15 categories. Each of the 15 categories has a various number of sub-categories. The item table has a one-to-one relationship to the 15 category tables (eg. tblCases.ItemID=Cat1.ItemID). Each category table has it's own unique...

Thanks, Randy & MajP! I'm beginning to see the light (sorry for my slow uptake). Certainly converting columns to rows by using a single Categories table should work! Why I have to make my work more complicated than it should be is beyond me. Thank you both for your valuable advice. Now I've got...

The data is a detailed analysis of a case. For example, "CaseA" could be represented on a report as... Case A: Category 1: SubCat 1 SubCat 2 ...etc SubCat 15 Category 2: SubCat 1 SubCat 2 ...etc SubCat 15 ...etc Category 15: SubCat 1 ...etc Each Category and it's...

Thank you for your advise. I should have stated that I had considered at least the first 3 levels normalization by placing each unique category into it's own table. There are 15 tables (one for each category). Each table holds no more than 25 fields representing it's own unique sub-category. The...

Scenario: An item can be assessed under 15 different categories, each category has between 15-25 sub categories. Most of the time a report would not need all of these categories and sub-categories. But (however rare it may) that all categories/sub-categores would be used, thus giving a report...

Everything is defined as a Date Type (variables and fields). The reason I even bothered to convert the data is that I have found date inconsistencies between machines - probably due to the locale setting. Anyway, most of the time I found converting to a string then do the comparisons have...

I haven't tried DateSerial yet. The machines that are misbehaving are in another building. I'm headed there to log onto one of the offending machines so that I can be a better picture (I hope). I'll keep you posted. Thanks again for the reply.

Thanks very much for your suggestion, but unfortunately the result has been the same. I've also tried other methods like... "Select * From tableA Where Format(aDATE,'yyyy/mm/dd')=#" & Format(myDATE,'yyyy/mm/dd') & "#" "Select * From tableA Where DateValue(aDATE) = #" & DateValue(myDATE) & "#"...

Using Access 2000 a recordset using a SQL statemtent similar to "Select * From tableA Where aDATE = #" & myDATE & "#" will work on one machine, but give a "type mismatch" error on another machine. I've changed the statement to read, "Select * From tableA Where CStr(Format(aDATE,'yyyymmdd')) ='"...

I stumbled on the solution by reinstalling a microsoft obdc driver. The function now works correctly.

I'm working on an ADP program using Access 2000 that connects to a SQL Server database. A few days ago, I tried to connect to the database using the "Connection..." menu option under "File" and nothing happened - no dialog window opened. I tried creating a new ADP using the wizard, again...

Thanks Missinglinq, I'll give it a try.

Thanks for the reply Missinglinq. I should have mentioned that equipment includes PC's, keyboards, mice (mouses?). The database front-end and mousehook.dll were replaced on the new drives from backups made before the equipment updates, while the back-end remained on the unchanged server. I even...