Stephen,

Now that we're on your favorite subject, SBT, and I am now working with the source, I too have question(s).

Whats the best way to set up your environment for debugging. I have to always remember to issue "On key label f8" so the business status report doesn't pop up.

Also, I'm trying to find where I need to put a call to an additional function during adding a sales order. If I open the Sales Order screen, there's a save button I can add my call to. However it appears that the save button is for line items. If I put a suspend in there, it suspends when I save line, but doesn't suspend again when saving the order.

PF

>>
>>Thanks tons! That's great information. If we do use SBT I will certainly be seeking more of the same :)
>
>Warning. SBT SUCKS, from a developers point of view.
>
>When you look at the source it's foxbase+ code that has been massaged over 7+ versions. Scary huh?
>
>Their use of visual oop is anemic. They have a procedure file that is close to a 1 meg file. First thing out of the box as a developer they want you to run a batch file to create the proc. EVERYTHING they do in processing runs through this f’n proc file.
>
>They don’t use a DBC.
>
>They don’t have any idea to data normalization! Use of a history file and double posting between current and history is enough to make you scream!
>
>Enough said.