Thank you Robert!

See my post here for some very good news: http://www.lantica.com/Forum3/cgi-bin/yabb2/YaBB.pl?num=1188761630/0#17

As for "everything under control"... well, no one else has fired up the app yet, so things are quiet here.  I expect the noise level to rise significantly around 8:00 when the Dispatchers punch in and have to make Workorders RIGHTNOWTHISINSTANTDAGNABBIT! to get the Riggers on the road.

Thanks again for your support, and thanks to everyone who has helped me get this thing off the ground.

Now if you'll excuse me, I've found 3 bugs already this morning, and have to do some re-programming.

Thanks Erika!

Well, I'm wrapping up the first day.  I am beat!  I only had two users powering it today, my Rigging and Trucking dispatchers.  The boss and the secretary took a few tentative dips.  Everyone is a bit wary because of the learning curve.

My Rigging dispatcher loves it, my Trucking dispatcher hates it.  But she's been generally cranky about everything today so I've taken her criticisms with a grain of salt.

We discovered a whole bunch of bugs right off the bat, but I think I've squashed them (I'll know for sure after I reconcile.)  There have been a handful of design changes requested, and I'll get around to them in due time (the one that has to go into effect RIGHT AWAY is a button to clear the Retrieve Spec, because the F3 key is just one too many keys for my boss to remember; he's already pushed to his limit with F7 and F10.  I pointed out that he could click on the Clear Form item on the command tree but he was unimpressed; he doesn't want to have to read either.  Sheesh.)

On the whole I'm pretty happy with how everything went.  A bunch of Workorders were created and printed, a bunch of Invoices were created and printed, today's incoming payments were posted and the reports printed, nobody crashed, and there were only a handful of "What the hell" cries floating through the air.  One occurred when my Rigging dispatcher accidentally put the letter R into the Workorder Number lookup field, which is a number element.  Sesame announced that it was converting it to 0, which resulted in a cascade of Writeln error messages when the lookup failed, and the entire form, which fills with lookup values, blanked.  Things were a bit tense for a few moments; error messages scare people, as does seeing all your data disappear before your eyes.

My only real problem was the printer issue I mentioned in another thread.  Also, now that my app is filled to the brim with Q&A data, some of the Lookups take longer than I'm used to seeing (and I had one complaint "this is slower than Q&A"  ).  I'll have to look into Preindexing again.

So that's the report from the field.  Cheerio!

Infinity wrote on Sep 4^th, 2007 at 8:27pm:

Make sure you are not doing more XLookups than you need. Commands like @XLookupSourceList can be real time savers.

Infinity wrote on Sep 4^th, 2007 at 8:27pm:


Excellent News!

Infinity wrote on Sep 4^th, 2007 at 8:40pm:


Yes indeed. You can, at any time, select File Save As from a client and make a backup copy of the whole app even when other users are using it.