Search results

Re: Testing data in batches, entering in table directly or create a "pseudo" table? The root issue is currently using only 1 sensor and testing a unit repeatedly instead of multiple sensors and testing a unit once. This involves a lot of time and moving back and forth by the testing tech. The...

Re: Testing data in batches, entering in table directly or create a "pseudo" table? no one?:confused:

Testing data in batches, entering in table directly or create a "pseudo" table? I know entering info into the table directly is a no-no, but that is what I want to do: we do testing and are currently using a excel sheet. We test 6 to 12 units at a time. all the units are run through each test...

may be oversimplified but what about an unbound field for input and running re query on lost focus? http://www.access-programmers.co.uk/forums/showthread.php?t=244719

Hi, I've been asked to find repair history in my access DB for any unit made in the past 10 years with a specific output range from an excel sheet and see if they have come back for repair in my access db. I have linked the excel sheet to acces and have a query to generate a list of serial...

thanks for the clarification of the logic

that's the ticket! I was trying derivatives of WHERE (([XRS-3 repair].[Serial #])Like "*([Forms]![XRS-3 Repair Summary by Serial #]![Serial #])*"); Thanks!

I have a query set up below which when launched, a pop up field appears to type in the serial number and returns all the repair entries containing that serial number. I want it to be able to return any serial numbers that contain a partial string in the pop up field ei: type "13" in the pop up...

can you post up your code?

then you did something wrong? the key is setting the the query to look at the unbound field on the form or report for the select criteria and setting the unbound field to "requery" on lost focus.

so sometimes walking away fixes things. it now runs under 10 seconds with a 2 year date range. slow, but acceptable, I suspect I wrote enough garbage code during the creation of the topic queries, that the back end db and server needed to be restarted to clear things out.

you have 4 "(" and 5")"

Thanks, I'll work on it and get back in the next day or two, have a wires melting issue to help figure out first. Oh if only everything could be fixed at a keyboard,,,,,

what are my "block sizes"?

Is this what I want to do? (method 3) http://www.experts-exchange.com/Microsoft/Development/MS_Access/A_9753-Creating-and-using-Temporary-Tables-in-Microsoft-Access.html

I want to split the difference of the data into 90 day groups.. as in unit comes in for repair [Date in] and IF comes back for repair between initial and next [Date in] in x days. group x in 0-90, 91-180, etc,,, only the [date in] is in a table, all manipulation after that is in a series of 3...

Thanks for the input, however your revised code takes approx 6 seconds to run, the original [Date Diff] code takes approx 2 seconds to run. and the extra 4 seconds is carried over to the [Date Diff Sum] query. :banghead::banghead: I think I need to do temporary tables. most of the articles...

Hi. The Question is "How many times has a [Serial #] been repaired and come back for repair in 0 to 90 days, 91 to 180 days, in a date range". The purpose is to quantify design or process changes impact on longevity. so I have a repair table that has all the info in it. Then a simple Date...

the more I learn, the more I am aware of and humbled by my ignorance :) now if I could find a mesage board as helpfull as this one for dielectric breakdown chemistry :banghead:

I'll remember to include the overriding question the coding question relates to in the initial post next time. :o