>Mr Rauh:
>Is there any problem with that, I mean, it to are they necessary for the overall functionality of the project, have you done any modifications on VAM. I will apreciate any comment....
>

For me there was. For example, I wanted to change the base behavior of numeric textboxes so that clicking on them would select the content in the same way that tabbing to them would. This could be accomplished easily by changing the parent class for numeric text boxes to add a few lines of code to the GotFocus event; it would not change the underlying accounting principles.

The VAM forms inherited from a derived textbox class provided by VAM. Without source, I had two basic choices - resort to instance coding on every numeric textbox in every SCX, and duplicating that effort each time a new form were released, or create a class derived from their class, and then write an app to hack their SCX files to change the class for each control that inherited from that class. If there were classes that inherited from the base numeric textbox class, I'd have had to construct subclasses of each control class that inherited from there and hack the SCXs...not a desirable thing from my POV.

Yes, not having source to the class libraries is a major impediment to customization from my POV. Yes, I've done moderately extensive internal and external modification of VAM to integrate with other products. And if I knew what I was getting involved with, I might not have dismissed SBT Pro as an unviable alternative because of the coding style when we "upgraded" to VAM. At least the source was available, no matter how much I disliked the coding style.

I certainly would not consider VAM as a desirable platform where extensive UI behavioral changes were needed. Integration with other software is not too difficult; there are reasonably good facilities for importing AR Invoices/Credit Memos, AP Vendor Invoices/Debit Memos and GL Journal Entries via text files, which I use to tie in with several external sources we've developed in-house for invoicing, production management, royalty payment and the like. Adding reports to a menu isn't difficult. Their data structures docs make me long for the SBT data file docs, and the lack of source to many internal functions and their UI classes in particular is an absolute PITA.

>>>Hi Norm:
>>>
>>>Thanks, but I'm working with SO,AR,IC ... well now you know the hell that I'm into.... I have done some modifications... but after hours of going trough the code and guessing and tracking down data on the files... I'm thinking in offer Visual Account Mate to my customers... I saw some code... and the code it's by far, more clear (at least to me) than PRO5....
>>>Thanks anyway.
>>>
>>
>>Before commiting to VAM, realize that if you buy the source you do not get the source to their class libraries.