Reply to thread

Message

[QUOTE="jwcoleman87, post: 169993, member: 50602"]
Thank you, I will try using the tag solution tomorrow, that way I can define everything at run-time (which is what I'm going for)

What I'm trying to accomplish looks like this:

[ATTACH]4184.vB[/ATTACH]

As you can see there, a serialnumber is selected in the working units list and it displays itself in the Unit actions group box, the status of the unit is also displayed.

Ultimately, I want to define what actions are available depending on which processID is held in the database. In unit repair I want the technicians to have access to a tab that allows them to order parts, in triage I want them to be able to select a root cause, in screening I want them to be able to give it a refurbishment grade.

Right now I'm experimenting with creating these tabs at runtime so that ultimately, depending on what the database will dictate. (What department are you in, which warehouse, what process step is the current selected repair in) - Okay you have these options available to work from.

I've been working to expand my teletrack application to be robust enough to be multi-departmental and multi-warehouse. For this to happen I need to move the framework to the database (all the stuff that determines what you can do when), and for the client to support it I need to figure out how to do all of this in a programmatic way that doesn't look like crap.

I appreciate your response and I will implement one of your solutions as soon as tomorrow. I'll let you know how it goes!
[/QUOTE]

Verification