Multiple "timers" in Access

[ptaleski]

Hello all,

I'm creating an application in ms Access 2007 that is tracking the time for baking for a group of different parts. Every part has a unique part number and "Level" which indicate after what time the part needs to baked.
I have about 500-1000 parts and I don't have any idea how to implement a code for a specific field in the table maybe.

Any suggestions how to solve this?

Thank You.

[Rabbit]

I don't understand what question you're trying to ask.

I don't have any idea how to implement a code for a specific field

You haven't explained what the code is supposed to do. As far as referring to a specific field in code, you reference it by name. The exact syntax differs depending on where you're trying to call it from and what the code is supposed to do but that's all I can say since I don't know what you're trying to do.

[zmbd]

ptaleski: If you are attempting to design a multi-channel timer on a form for process control, that may not be possible.

The only way I see this working is to setup a form timer event that checks to see which projects have been initiated and compare the recorded start time against current system time to determine if the elapsed time has been met against your data. (sounds better in my head ;-) ) This would be a variation of the many idle state timers we've covered here on bytes.

To explain the "initiated concept" the record would have code behind it that caused the initial system time to be recorded against that row/object when an on_click event is tripped.

This is a kludge method.
I work for/with a very large industrial processes and we have process-level-controllers for the various parts of the plant that the controlling database pushes the timer events to... even though we have multiple servers, we have 10,000x that in smart control cards.

If this isn't what you are after, then I am swimming along side that boat that Rabbit is paddling!
-z

[ptaleski]

zmbd Thank You for your view on this matter. It is a great idea but still it will solve me only half of my problem.
Let me explain in more details what I'm trying to do:
I don't know in which branch of industry your involved but my problem is about controlling the moisture sensitive level(MSL) of electronic parts. Every level has it's floor time and this time passes this parts have to be baked for another usage.
Your idea can solve my problem with the level 2 parts which have 1 year floor time and they are stored normally. But levels 3,4,5 when are not used are stored in dry cabinet which pauses this timer. So every time part is in dry cabinet the timer must be paused, and here begins my problem. Implementing timer for level 2 it can be done as you suggested because time is running non-stop for all this level 2 components. But how to solve for the other levels..
I was thinking if is possible to run some code with timer that can be paused, on every field in the table in access(similar as Excel)???
I don't know how to wrap my head around this?
If You have any suggestions about the logic how to solve this I will be very grateful.
Thank You..

[zmbd]

Hmmm.....
You could build a query against the records to pull those that meet or exceed the time limit the same way that one for a hotel room booking which is similure in concept to what you are doing... checking each part into and out of the "room" to dry out.
Use the form timer event to run the query every say... hour or so, or less depending on the tolerance of your process, so that your parts are listed. Use conditional formatting against the time limits to help visulize the priority parts, etc...
You may require something more robust as you database grows such as one of the SQLServer, MySQL, Oracle to hold the data on a server level so you will want to pay attention to proper normalization rules to allow for easier future upsizing!


Forgive any typos sent from my tablet... My PC fried itself��

[ptaleski]

Zmbd Thank You a lot!!!
I will try to put this in practice and hope that will work :)

You are right about using more powerful database but my friend Access is the only legal platform at work that i can work on :)

Thanks again and I will write when I will be done...

[zmbd]

Of course if we can help post back... Go ahead and post related question here.. If needed we can start a new thread :)

[jforbes]

Just to expand a little... this sounds a lot like a Parts/Warehouse Inventory application. Typically in tracking inventory of this nature, the parts are either lot tracked or serial tracked meaning the parts are as a group or individually given a unique number to track them as long as a company has them in their possession. FDA requirements can take this to a completely different level and you would not want to attempt tracking that inventory with a homegrown solution.

So the basic Inventory application does this:

• Receives parts, initially creating the tracking number.
• The parts are placed in a stocking location/warehouse.
• As they are needed, an order is placed (internally or externally) and the parts are either moved to a different stocking location/warehouse or shipped which would remove them from inventory.

For a more thorough definition and a cure for insomnia, internet search for MRP (Material requirements planning) and MRP II (Manufacturing resource planning )

As the parts are moved from warehouse to warehouse as well as receiving and shipping, a transaction is placed in a history table that contains the lot/serial number, date of transaction, and warehouse location. Typically, it would be this history table that is queried to get the information you are looking to track.

[zmbd]

J, IMHO, much better analogy... guess we could look at people like inventory };-)