>>How do you use Quickbooks to keep track of endusers??? The invoicing part I understand, but then how do you get the contact, serial, version, etc. into the "other" program???
>
>That is something I am working on now. It's a registration service for our app setups. We will [also] be logging (hopefully very few) desktop error messages. An IIS ASP/VFP server will collect registration information, capture, log and route desktop errors and manage renewals. On-line help is another consideration.
>
>We are also requiring our users to purchase a VFP license. It's a good value and should help with any data issues. Are you including a VFP license with your distribution package?

When we sell our software, they are automatically registered by us at the time of the sale. Most (99%) of our sales are direct, so we don't have a lot of users who are purchasing our software from a reseller and then calling us to register.

The time-line runs something like this...

1. Invoice for new order generated.
2. New user information transferred to user file.
3. Annually, we send out upgrade information because we issue annual upgrades. Includes support. Upgrade notices are generated from our application.
4. Upgrade orders entered and endusers information automatically updated to reflect upgrade (version and date upgraded).

Certainly somebody has created an application for the independent software developer... or someone should!