Finally got the MSDN version of VS 2005, so started on a new project, put a list box on a windows form, wrote some code, ran it and "whoops".
PROBLEM 1
========
on the .clear() method, VS is grumbling about writing to protected memory, see below.
System Exception has Occured.
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at LpLib.IfpList.Clear()
at AxLpLib.AxfpList.Clear()
at Rolex_UK_Offline.frmSearchOrg.frmSearchOrg_Load(Object sender, EventArgs e) in D:\Visual Studio 2005 Projects\Rolex UK Offline\Rolex UK Offline\Names and addresses\Search Organisations.vb:line 17
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
at System.Windows.Forms.Control.Show()
at Rolex_UK_Offline.frmMain.CreateCallReport() in D:\Visual Studio 2005 Projects\Rolex UK Offline\Rolex UK Offline\Starting Up\Offline MDI Background.vb:line 262
In frmMain (CreateCallReport)
PROBLEM 2
========
On the windows form designer, I anchored the list box control for top left bottom right, resized the form. I can see the list pro control going nuts, as it's got stuck in an endless loop while trying to sort it's vertical size out. It looks like well, hmm. It draws itself, then shrinks itself, then grows, then shrinks and you can see the bottom of the list trying to do its stuff, and then the Dev Environment is running at 99% CPU. You can cure this by right clicking on the project in the taskbar. and the form and the controls go back to their original size. Bit weird eh?
QUERY
=====
Is this normal?
I add the Farpoint List Pro 3.0 Controls (Interop.LpLib.dll) as a reference in my project, so what is this that gets added?
AxInterop.Lplib.dll (in the bin\Debug folder)
And my list controls appear to reference this.
Any help appreciated
Cheers.
Greg Russell.