No luck yet...

I have tried triggering the code using multiple ways and I got nothing so far.  Anybody have any ideas on triggering Sesame code from a web based record being created?

-=K=-

I am using an internal Sesame server. 

I already have a client running the application on the server machine.  Sesame requires this as a security measure in order to update/add records to a database from a webpage. 

An interval is not a bad idea...hmmmm...

Originally, I wanted it to print the moment we received the order, but I suppose I could try it with a moderate interval and see how that goes.  Excellent idea, I'll give it a try.  However, I wouldn't even know where to begin telling Sesame to only query and print new orders, as opposed to those already printed.

Perhaps I could make 2 separate databases:

1 That collects the requests and hold them for a specific interval.  It then prints ALL its records, copies those records to another database, then deletes said records from it-self.

It might work.....yeah.....it has to work....

Until tomorrow!  Ill keep you posted...

-=K=-

I cant come up with a way to get the print timer working without completely locking up the application:

I tried using For/While loops on Form Reveal and this locks up the application before the form loads.  I'm using @ServerTime to calculate the print job in 1 minute intervals.

I tried using "Loiter(60000)" so the code block would wait 60 seconds before running again.  However, this seemingly locks up the application entirely for that 60 seconds. 

Neither option allowed me to load data into it from the webpage because the loop (obviously) is never being left on Form Reveal.  Perhaps I could try attaching it to a different element - not sure if that would make a difference or not.

Does anyone know of a way to run a piece of code, at an interval, without using For/While loops that hog up control of the program and prevent adding data?

The Cow = The Genius

After some stumbling over the syntax, I got this command to work.  I'm ashamed I didn't come across it myself while pouring over my programming guide. 

I now have a button on the server-side application that can be pressed to "Start Auto Printing."  Another press shuts it off. 

Now I know how to automate the code, its only a matter of changing it too pull the correct records and alter them after they have been printed.

Thanks for all your help Cow, I'll let you know how it turns out.



-=K=-

Success!

Application is working as intended so far.  Users all over campus can now access the local webpage, fill out a form, and it prints at the maintenance shop automatically.

The program scans its records once every 60 seconds ( I may change this as the database grows ) and finds records that have not been printed.  It then prints those records and sets the records as "printed." 

When accessing the application directly, edits can be made to records and the status changed to "not printed;" this will force the record to print on the next cycle.  A "print now" button could be added easily.

There are a few minor things I need to fix with the format, but otherwise it seems to work pretty well.  I tested it's ability to overcome tragedies, like when the printer jams or runs out of paper:  because all printing is done through the spooler on the server system, the jobs are simply stored until more paper is fed to the printer.  I may try a more extensive test of this later...

I'm not too worried about security at this point, as the data is backed up and it's not sensitive.  The next thing I will add is attaching a unique ID to each work order as it is created, as well as a few bells and whistles to make the application easier to work with.

Not bad for my first real Sesame application.  Thanks again to "The Cow" for all the help. 

-=K=-