>As much as I want. The key is understanding accounting as well as FoxPro. Otherwise, you can get requests to do shady things and do them because you don't know any better.
>Know what? The IRS doesn't care if you didn't know it was wrong -- you can still end up in jail. Also realize that businesses rely heavily on their accounting systems. Making a mistake in this field is akin to making mistakes in surgery.
>Other that that, it's pretty good. Although SBT doesn't exactly tax the limits of VFP -- at least not in its present forms. More like FoxPro Windows and a smidge.
>- John


PMFJI, but most companies don't want you to change the way SBT works, they want added functionality, Decent reports, timely data analysis, different module data in an existing module, etc.

SBT isn't bad, but it isn't great either. Most users I have dealt with need sophisticated data viewing, as well as SOP modules that are missing from SBT.

SOP issues are:
1) Bills of Lading
2) Label production for shipping
3) Paletizing shippments
4) Customer payment analysis in New Sales Order
5) Credit limits that are product type specific
6) Automated notification of order cancelations
7) Productivity reporting from a HR point of view

The list continues but I've got to fix some of those issues myself.

Stupid SBT Ideas!
xxYtttNN history files!
Leaving data in current as well as history for open items
RPITA tracking between SO to AR !
No ability to credit customer for negociated pricing and discounts _RECEIPT
No data normalization to speak of
Use of the Date Field, need I say more?
Indexing on functions!
Inability to add a column to a table without using their update table prg.
No data dictionay in ERWIN or xCase
Letting CPA's change the code
SBT CODE !!!!
Terrible documentation

Damn, I have to get back to those other SBT issues, I was having fun here.

__Stephen