Re: The future for Legacy?

Paul Blair <pblair@xxxxxxxxxxx> wrote in
news:43a9cd76$0$17702$afc38c87@xxxxxxxxxxxxxxxxxxxx:

<snip>
>
> Sherry is not really listening, I feel. So be it...it's her future!
> Or not...
>
> Paul

Ummm..... still waiting to hear what you think needs to be in a
genealogy program..... Unfortunately I missed the message that you
referred to.

Enhancements to Legacy are customer driven. Obviously, the programmers
can't include *all* enhancements that are requested, but all of the
requests received are logged and reviewed. Some unfortunately are just
not feasible in the program due to the background structure of the
database but the vast majority of enhancements are as a result of
suggestions from customers.

For example, the Publishing Center - we've had a *lot* of request for a
way to create a book that would include various types of reports with
one index and TOC for all of the reports - and that was a major new
feature in v6. Timelines were another much requested feature.

So if you're a Legacy user and have any great ideas for us, feel free
to email them to me directly to Support@xxxxxxxxxxxxxxxxx and I'll add
them to the list.

Not surprisingly, many features requested are already in the program
and the users just haven't found them yet!

Sherry
Customer Support
Millennia Corporation
Support@xxxxxxxxxxxxxxxxx
http://www.LegacyFamilyTree.com
.

Relevant Pages

  • Re: Added header info form a BHO
    ... customer wants to add a feature that will add add an X-header to all ... requests when the user is logged into there web application. ...
    (microsoft.public.inetsdk.programming.webbrowser_ctl)
  • Re: VB.NET and SQL
    ... what it might be used for I think you can see that it isn't a concurrency ... Imagine three users needing to obtain the "next customer" from a pool of all ... It isn't an "update" problem and the requests need to be queued. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: VB.NET and SQL
    ... what it might be used for I think you can see that it isn't a concurrency ... Imagine three users needing to obtain the "next customer" from a pool of all ... It isn't an "update" problem and the requests need to be queued. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: VB.NET and SQL
    ... what it might be used for I think you can see that it isn't a concurrency ... Imagine three users needing to obtain the "next customer" from a pool of all ... It isn't an "update" problem and the requests need to be queued. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: VB.NET and SQL
    ... what it might be used for I think you can see that it isn't a concurrency ... Imagine three users needing to obtain the "next customer" from a pool of all ... It isn't an "update" problem and the requests need to be queued. ...
    (microsoft.public.dotnet.framework.adonet)