Yo, Ren!

Actually, they had me dumb the final version down to link to their Word documents. The original data-structure and job building blocks was still available, but they preferered to invest their time into manually updating their Word documents. Just like the staff we worked with, and sometimes resembled, it ended up a queer solution. It seemed "clear" to the users though ;)

Doug - AKA "Stimpy"

>Doug,
>
>I remember that. Excellent application; slick and intuitive. They changed the specs in the middle causing you a whole lot of extra work if I recall correctly. Something to do with a "split" and trying to change the way the logic branched wasn't it?
>
>Renoir
>
>
>>John,
>>
>>Begin with a process flow diagram, build an ERD and design the database BEFORE you bother with the UI presentation. I've actually written a program back in my VFP 3.0 days that did this very thing. Unfortunately, the employer who has the code went belly-up.
>>
>>In the system that I designed, every program was accounted for separately - providing instruction on running the program. Then, I had a jobs table that had the desired programs referenced in the sequence that they were to be run and special overriding instuctions as needed. In the environment that I worked in, a program may be used multiple times during a given evening shift - depending on the processing needs. These jobs were then assigned to a specified schedule / interval. (e.g. every Wednesday, every third Monday, last business day of the month, end of quarter, etc.)
>>Also, I believe that these jobs had a sequential order with dependencies.
>>
>>Good luck.
>>Doug
>>
>>>I need to write a scheduling system in VFP 7.0.
>>>
>>>The purpose of this scheduler is to schedule production runs on machines.
>>>It should be fairly simple in design. Any job number (coming from a work order table) not yet scheduled can be appended to the end of scheduler (list type) OR be insterted between other jobs also.
>>>
>>>All jobs should be allowed to be moved around at any time. The visual order of the jobs is the actual order the jobs should be done. There are approx. 100 jobs (maximum) that can be scheduled. Also I need to select the type of run of the job, "Regular", "Combo", or "Split" preferably from a drop list selection. I also need to add comments, trigger events and perform validations, etc. for every job/line added.
>>>
>>>Does anyone have any recommendations on what I should use to do this?
>>>Will a list box interface be adequate for this design?
>>>
>>>Thanks to everyone for thier advice.
>>>
>>>John