Replies

I agree that you need to provide more detail for us to help.

I find that complex queries in Access often fail. To keep track of the bits that do work, I use a simpler query to make a table … then query the new table with the next bit to make yet another table … and so on.

This way I can interrogate each table to test the effectiveness of the process/code.

Once I get it to work, I try to assimilate the various steps.

Some of my commercial products still use this approach, but driven by a form which asks the customer to click on a number of steps.

This is a linear regression exercise – I do not think Access has a function available, so you would have to build your own function.
It is similar to the SLOPE function in Excel. The formula is in the following link:

Excel Tutorial on Linear Regression
phoenix.phys.clemson.edu/tutorials/excel/regression.html

If VBA code is not your thing, you could do bits of this with update queries into a temporary table.
You would need to set a start date and an end date for the data set

One method that I use sparingly (because it creates a non normalised situation) is to use code to enter the name ( or whatever piece of information) into a new field in the slave table. The code could run through all your records and record the name. Then you can browse through your slave table and see the name. Use a form to view the record with the Name field locked to prevent accidental editing of it.