>Hi, John!
>
>I hope Frx2Word can be used together with GenRepoX as many of us are relying on this tool for our reports!

Give John a chance - this is a first cut at the tool, which he's put a whole lot of effort into, from a pool of rapidly shrinking free time. I do know that John has been intending to contact Marcus regarding GenRepoX, but have no idea of what accomodation of GenRepoX will be made. The tool should be viewed as a first open beta, and in a practical sense, new demands for features, compatibility with third party tools and the like should be forwarded to the bit bucket. Immediate concerns are real bugs and improper reproduction of the behavior of FRXs as they are now implemented.

I spoke to John tonight. There will be a new version in the next couple of days with some neat new features. He has not yet talked to Marcus about interaction with GenRepoX, and given other issues on his plate, and a wife and kids who'll probably kill him if he doesn't spend a day with them rather than locked in a room coding, it won't be addressed instantly

There will be future releases as time permits. THere are known issues with emulating the internal implementation of some features. John worked long and hard on this, and the decision was to fit the FRX behavior, even where we thought the FRX behavior was not how we'd like certain things to act in VFP reports but don't. Reality - you may be disappointed that it doesn't integrate with GenRepoX. I know that in the tests of earlier versions that I did, I did not try any GenRepoX-based things.

Report bugs. Thank John for his efforts. Suggest enhancements. Don't make demands unless you're willing to pay John for his time at his regular billing rates - eSolutions Services is a full-time job for us, and aside from being overworked by paying clients, he has a wife, a couple of kids, a house, a backyard badly in need of landscaping (unless things have changed since I last visited) and commitments for things like DevCon, and all the headaches of a new startup company. He's up on UT and the newsgroups. And that's just part of the fun.

Seriously, if you want specific features and compatibility added to the product, feel free to drop us a line. If you're willing to pay to have them added, we'll put together a proposal, and should you accept, put staff on it during business hours and try to meet a delivery schedule acceptable to you.

The argument - "release it as shareware - I'd pay name an amount, and with 500 people registering the shareware, you'd make a mint!" does not work. Shareware as a concept very rarely works. I know - I've released lots of it.

Be assured there will be a commercial release for a reasonable price, which will have added features. This isn't it. It's a neat piece of code that was given to us, built in someone's spare time. If a commercial grade offering at a commercial grade price is a requirement, tell us - we've three reasonably competent partners in the firm (John Koziol, Craig Berntson and myself) and can bring on other resources when needed, but we've got to make a living.