I'm wondering if the Aronow Static Data Supplier still works with WLP6. I reinstalled it, so the .dll is in the WLP6 directory. I still have the datasets in WL4...Old15min and OldDaily. In WLP6, OldDaily didn’t show up anymore (not sure when it disappeared). So I tried to recreate it with Create a new DataSet | WL4 Files | Wealth-Lab Pro 4 | Select an existing DataSource from Wealth-Lab Pro 4 | Old Daily…Boom AccessViolationException…

I also sent Dave an email...

Jim,

Are you referring to the Watchlist Static Data Provider (WL extension)? As far as I know it works with Wealth-Lab 6.0 32 bit although it may not work with 64 bit (if it does not I will update it sometime in the near future).

Based on your error I'm not even sure if you are using the watchlist provider or possibly the native WL4 provider (which is part of WLP and has nothing to do with my adapter). Can you please provide more information?

Dave

P.S. I'm responding here instead of via email since this way other users with the same question can see the answer

Duh, you're absolutely right. I tried so many things trying to get something to work I got confused...

So, I'm using WLP6 on a 32-bit XP computer and the native WL4 provider threw an exception. I reproduced it several times. See my first post for details...

I renamed the topic so not to confuse anybody - the Watchlist provider has nothing to do with reading old WL4 data files.

On 64-bit operating systems, "Select an existing DataSource" is disabled in 64-bit mode (but you still can select it if WL6 is run in 32-bit mode on a 64-bit OS).

Selecting an existing dataset does work on a 32-bit XP computer.

* Did you select the Wealth-Lab Pro option in the wizard, or was it WLD?
* Which exact AccessViolationException message do you get? Can you expand the exception box and copy the details here?

I took all the defaults in the wizard, so yes I use and selected WLP. As it turns out, the solution to my problem is in another direction and I don't really care about this, but I'm happy to help. Here's the exception details:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at g.GetDataSets(String A_0, String& A_1, Boolean& A_2)
at g.b(String A_0)
at g.a(String A_0, Int32 A_1)
at WealthLab.DataProviders.WL4Files.WL4StaticProvider.PopulateSymbols(DataSource ds, List`1 symbols)
at WealthLab.DataSource.get_Symbols()
at WealthLab.DataSourceTreeView.a(TreeNode A_0, DataSource A_1)
at WealthLab.DataSourceTreeView.ItemAdded(DataSource item)
at WealthLab.DataSourceManager.Add(DataSource ds)
at d1.b(Object A_0, EventArgs A_1)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
...
----------------------------------------
WealthLab.DataProviders.WL4Files
Assembly Version: 1.2.5.0
Win32 Version: 1.2.5.0
CodeBase: file:///C:/Program%20Files/Fidelity%20Investments/Wealth-Lab%20Pro%206/WealthLab.DataProviders.WL4Files.DLL
----------------------------------------
...

Thank you. I'll pass this over to the relevant person.

One more tidbit. I checked the database path the wizard gave me and it's correct and the dates in that directory are recent. However, that's not where I keep the .WL files. Very early on, when the feature became available, I specified my own directory where I keep all the fidelity data. Don't know if that's relevent, but...

Your data was relocated - knowing this could be helpful, thanks.