Hi,

Pls can you assist before a buy the WL DEVELOPER 6.1:
1) Is the license fee an annual pmt or once off?
2) If a new version is available after purchasing, do i pay the full license fee again?
3) I have a Mac and run Parrallels for my Window apps - any issues from users with this set up?
4) Diff betw 32/64 bit?

Tks

Hi,

1 - There is a license fee ($799) and an annual payment i.e. maintenance fee ($150, starting from 2nd year).
2 - No. While your maintenance period is active (i.e. during 1st year after purchase when maintenance fee is waived or later if your maintenance fee has been paid), upgrades are free.
3 - Many users run Wealth-Lab Pro and Developer in Parallels, no known show-stopper.
4 - Key points summed up in this FAQ: Is Wealth-Lab Developer/Pro 6 able to use 4(6,8...) Gb of RAM when running on a 64-bit OS?

QUOTE:
3 - Many users run Wealth-Lab Pro and Developer in Parallels, no known show-stopper.

Does that mean a Fidelity customer can download and install WL Developer? If not, how does one get both versions?

Absolutely not, I mean to say that both Fidelity and our customers are using Parallels.

Tks Eugene. I have now purchased WL Developer and working with it using Parallels.

One, possibly silly, question: how do I make use of the mouse 'right click' actions e.g. in the dataset menu?

Hmm, you just click there and a popup menu appears. What's your experience? Please describe step by step.

Apple help showed me how to do it, tks. I have been testing, using and learning the WL software until yesterday. The following error msg came up:

[Window Title]
Microsoft Windows

[Main Instruction]
WealthLabDev has stopped working

[Content]
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

[Close program]

"Windows" has not "notified" me and I'm at a loss as to the solution. Can you assist or shall i create a ticket for support to revert?

Tks
Anthony

Yes, please enter a new support ticket.

Apologies Eugene. Tried 2x but following error when trying to submit ticket:

Bad Request

HTTP Error 400. The request is badly formed.

Try clearing cookies and re-trying. If still no go, try later or try in a different browser.