The file WLP-to-WLD migration tool gets confused when it does the migration. It wrongly thinks my datasets are in the Administrators' directory, and they are not. They are in my personal user's directory instead. The solution there is to not run the tool as Administrator; otherwise, it uses the wrong directory.

It migrates all the WL config files just fine, but the Fidelity datasets aren't converted to IQFeed datasets as I want. That's fine; I can recreate those manually.

But the strategies weren't migrated. I can copy those manually, but how do I migrate the Summary Description for each strategy? Where is that data stored? That description is not in the strategy source (XML) file.

QUOTE:
And why is the Data Tool not showing any datasets? How do I fix that? See attachment.

It does not belong here. Please use the existing forum topic for the unrelated question.

QUOTE:
the Fidelity datasets aren't converted to IQFeed datasets as I want.

It's not even advertised that DataSets would be converted. Maybe we add such enhancement at a later time but decision is not made yet and development hasn't started.

QUOTE:
The file WLP-to-WLD migration tool gets confused when it does the migration. It wrongly thinks my datasets are in the Administrators' directory, and they are not. They are in my personal user's directory instead. The solution there is to not run the tool as Administrator; otherwise, it uses the wrong directory.

Passing this on to Cone, the Migration tool's author.

QUOTE:
but how do I migrate the Summary Description for each strategy? Where is that data stored? That description is not in the strategy source (XML) file.

Wrong. It is stored within the Strategy's XML file. But first let's find out why the Strategies aren't migrated.

QUOTE:
Wrong. It's contained in the Strategy file.

Well, you must be right. The Summary Description must be in the strategy source file because copying the Strategies folder over to the appropriate WealthLabDev subdirectories works as expected. The Summary Description is correctly copied too. Thanks for the help.

QUOTE:
It's not even advertised that DataSets would be converted. Maybe we add such enhancement at a later time but decision is not made yet and development hasn't started.

Right. I'll just recreate them manually. I only have about 40 files. I did think about using an awk or perl script to do this "stream editing", but by the time I would get the stream-editing script done I could have converted them manually.

With 40 files, you would certainly get it done manually before we're warmed up for development! :) It might be a convenience to translate the Fidelity specific symbols into those supported by other providers (.SPX > ^GSPC, BRK.A > BRK-A for Yahoo, .MB_ADV.Q to Wealth-Data's $NASDAQ_ADVN etc.) For simple stock symbols it's a matter of copy/paste.

QUOTE:
It wrongly thinks my datasets are in the Administrators' directory,

You should log in to Windows with the user account that uses Wealth-Lab. Then, right click the tool to "Run as Administrator".

The migrator copies each directory in the WLP Data folder whose name doesn't start with "Fidelity" in order to skip copying the Fidelity provider data folders. The migrator doesn't do anything special to copy the "Strategies" folder. (It also copies the DataSets folder, but intentionally skips copying Fidelity Provider DataSet files since that Provider will not exist.)

Did you happen to copy the log? In retrospect, we should have saved a migration log file.

QUOTE:
You should log in to Windows with the user account that uses Wealth-Lab. Then, right click the tool to "Run as Administrator".

That's what I did. The problem is "Run as Administrator" makes the OS think your %USERNAME% is "Administrator" and not "mehl" (which is me), so it goes into the wrong user directory even if you're in the "mehl" account.

There's probably a way to force %USERNAME% to be "mehl" when running as Administrator, but I don't know how to force that. Perhaps I need to execute the mehl profile to force it. I'm running Windows Ultima.

No I didn't save the log.

Hmm. Okay. It's actually getting the username from Application.UserAppDataPath. I suspect that changes if the current user isn't an Admin. I'll work on that. Thanks.

New Version 1.2.0.0 migrator is in place (same download link) that provides a "good-enough" solution for the case in which the user is not also an Administrator.