Search results

You need to change the type of 'join' you have made in your query. I am not on a PC with Access right now, so the following is from memory: If you 'right-click' on the actual join line between your two tables in the query design form, you should get a dialog that allows you to pick one of...

You should be able to import data of 255 characters into a text field without chopping at 50.

It would simplify your problem to do a bit of massaging in Excel first. Create an 11th workbook to bring the 10 SD values via links into one 'table', with a column that suitably identifies which SD it is, and one for the actual value of the SD. Give this a range name in Excel, such as 'AllSDs'...

In your query, use the Format command to create new fields like: LoginDayHour: Format([YourDateTimeField],"YYYY-MM-DD HH") This will generate a unique value for each hour of each day LoginHour: Format([YourDateTimeField],"HH") This will generate a unique value for each hour of the day, but...

Assuming your table has an autonumber id field: In a query, make a calculated field as follows: RandomLetter: = Chr(Int(Rnd([Your_ID])*26)+64) The Rnd function generates a pseudo-random number from 0.000 to 1.000 using your unique ID as the seed (making the value reproducable, by the way). If...

You may be better off by creating a 'lookup' table with fields for MT_ID, MType,LookupValue, and then relating this table into your query. This eliminates your extremely ugly IIf expression, and makes maintenance MUCH easier, as you can add, change, or delete the lookup records very easily...

I'm glad you found a way to solve your problem. I didn't realize that you intended to take the 'average' value and relate it back into your 'first' query. I expected that you would relate this value to a NEW query that also used your original query as source, as there would then have been no...

I agree with what Len had suggested, except: You should be able to make a summary query to calculate a single average value for 'baseline' and use that as the subsequent source where he suggests using table 'temp'. Obviously, the resulting query will not be updateable, but I don't think that...

Try "MIN" rather than "FIRST"

Use [Forms]![YourFormName]![YourTextBoxName]

I have had this happen to me, and it was a matter of adding the appropriate reference in VBA. I do not remember the specific one, however.

It is usually considered a bad idea to use the table view to directly manipulate data. Purpose-built forms allow for better input control and data validation. The 'rule of thumb' is: Tables store data. Queries manipulate stored data. Forms allow on-screen input and output of data to tables...

Grouping together related records can be done easily by suitable sorting. In a query that contains all of your relevent fields, the first (or 'leftmost') field in the query design grid that specifies a sort order is always sorted first, following by the second, etc. Filtering in a query is...

Do you mean to redefine a table's structure for text fields to ensure that they are large enough to STORE the data, or are you referring to adjusting the width of control(s) on forms or reports to DISPLAY the data? If storage is your issue, setting text field sizes to 255 doesn't really waste...

If you create a summary query, you can use "group by" for your date field and count/sum of the source to show the statistical data for all months, and use a filter if you only want to see the current month. Then you need not store any data.

As far as I could find, Access does NOT allow for MLR 'out-of-the box', although you CAN buy some addins that do it for you. I have gotten around that by 1) exporting the relevant data to Excel, and crunching the numbers there 2) developing a general 'module' that uses Simplex Optimization to...

First and last post to this thread: At the risk of putting a figurative hand in the middle of a catfight: Both sides on this 'debate' are right, and both are wrong. Mike can make his application ANY way he likes, so long as he is content with the way it works. Although he may actually...

If you are not adverse to a bit of code, write a function that selects all of the course records for a given instructor, and then concatenates them into a single string, which is then assigned to the function return value. Then you can easily write a query that shows each professor and a...

If your query does not show any fields from the Areas table (just events and contacts), then your example should create two identical rows. Look up the DISTINCT and DISTINCTROW query modifiers.

On the other hand... Have you thought about simply performing your analysis in 5-year 'steps'? Each cohort will then age exactly enough to simply become the next cohort. Once you have that done, you can assume that the results are reasonably accurate for the 'median' age member of each...