Runtime error after hitting the button 'Run WinBUGS'

[PW]

Hello,

After purchasing and reading the book, I tried to get some hands-on practice starting with Case 3.1.

Unfortunately, after following all the steps and hitting 'Run WinBUGS' I get the following message:

Run-time error ‘2110’:

Can’t move focus to the control because it is invisible, not enabled, or of a type that does not accept the focus.

I've installed everything correctly (incl. WinBUGS14) on a 64-bit Windows 7-machine.

Any advice on this is much appreciated!

[PW]

In addition to my previous post on this error message, I would like to add that I am using a 32-bit Excel version on a 64-bit Windows machine..

Has anyone perhaps encountered the same problem in this situation and has any advice on how to overcome the problem?

Thanks in advance!

[George Ellis]

Hi PW,

I am sorry to see that you have not solved your problem.  This is not an error that I have had or heard of until now.  However, having said that, you really have not provided much detail beyond this error.  Unfortunately, I have not worked with bugsXLA for several months now.  In addition, I have since rebuilt my workstation and have still not re-installed either WinBUGS or Phils addin.

However, I wonder if you are not experiencing an issue that a few correspondents to this group have experienced when doing their first example 3.1.  This may be of no consequence but this is some advice I gave to another user who had errors when executing Ex 3.1:

" I had opened the spreadsheet and started working on the example before I realized I needed the F2:F3 cells arranged as indicated in the text.  (The spreadsheet - as you know - does not originally have the text filled in).  So I exited BugsXLA and then filled in the cells in the Excel spreadsheet with TRT and * and then saved and closed Excel.  Then I restarted Excel and the BugsXLA Add-in and the example worked without the error.  Without doing further investigation, I assumed that once the Add-in starts running, it does recognize changes to the spreadsheet that was open when the Add-in first started."

So, if you load a spreadsheet and then start BugsXLA - but then you alter cells outside the "focus" or state of the spreadsheet you may get errors like the one you have received.  Try exiting Excel.  Reload the spreadsheet.  First make the modifications you want to the spreadsheet - like adding cell headings or parameter/variable information.  Save the spreadsheet with these modifications and then load BugsXLA and execute the steps required for your analysis.

If you can provide some additional detail - please do.  As for Excel 32-bit running in a 64-bit OS - that is pretty much everybody's setup and it should not be causing you any difficulty.

[PW]

Hello,

I have still not been able to solve the problem. It is not a problem with the saving of the file, since it persists even after saving the file, exiting and reopening.

The same problems occurs also with any of the other worked examples.

In addition, I have tried to install it on a different machine (a laptop with 64-bits Windows 7 and Excel 2007), but get exactly the same error message.

One additional detail I can add is that when I click on the BugsXLA-options button on the Excel add-in taskbar, I get the following error message:

[Window title:]  fmBugsOptions_Initialize [Message:] Could not set the Value property. Invalid property value.

When I click 'OK' on that error, I do get the options menu...

I really hope that there is a way to get it to work, but I do not have a clue what's causing the problems.

[Barbara Reichmann]

Hello!

I'm experiencing the same problem when I try to do case 3.1.
Both error messages mentioned before appear as well.
In addition when I check the options I get the following error message when saving:

Prior for Gamma
Uniform prior parameters invalid:
(0.1<=g1<=g2<=9.9)

When I change the values in "Default Priors 1" according to the ones mentioned in section 2.12 most is saved correctly but when I reopen options again the following values remain unchanged:

Outlier Model Parameters
Prob 0.1 (insead of 0.05)

Random (Exchangable) Effects
Distribution with scale parameter
Half-C (instead of Half-N)

The same happens to all the changes I did to "Default Priors 2"

I don't know if this has to do with the original problem but maybe it helps to find the cause of this mess.

I'm thankful for any suggestions!

Barbara

[Barbara Reichmann]

Hi,

I solved my problem via changing absolutely every langugage settings I could find: Win7 (the whole operating system as well as "format" and "current language for non-Unicode programs" under "region and language") and MS Office.