www.cmm.bristol.ac.uk/forum

This may just be a display issue, if it doesn't crash or give any error messages then you should get the same results regardless of the display format. One thing it might be worth watching is the commands generated in the "command interface" window. If numbers sent to these commands appear...

Could you also please let us know whether you still get the "line too long" message after removing the cases with missing values?

This kind of message is often a symptom that the current worksheet size is too small. Instructions for increasing this can be found at:

http://www.bristol.ac.uk/cmm/software/s ... eworksheet

This appears to be a bug in the software. As a workaround if you enter the command:
in the command interface window it should have the required effect.

Thank you for reporting this bug, it will be fixed in the next released version of MLwiN. In the mean time I think the only workaround would be to manually generate row and column codes (with a maximum of five unique values in each) where each combination corresponds with one of your current codes a...

Unfortunately I don't know exactly what is causing this problem as it is occurring in the graph component, which is provided by a third party. It may be that this component is conflicting with something else installed on your computer, but this would be hard to track down. One thing to try would be ...

You can set the category labels from the names window (Data Manipulation->Names). If you highlight a categorical variable and the click the "view" button in the categories section then you will get a window containing a list of categories defined for that variable. If you edit the name her...

To avoid this message you need to convert your variables to have a lower precision before sending them to MLwiN. If this is possible without losing accuracy then the Stata command http://www.stata.com/help.cgi?compress will perform the conversion for you, otherwise you will need to reduce the precis...

I have just tried this example here and it appears to work fine for me. Could you check that your version of Stata and runmlwin are up to date? If you still have problems could you run the command: set trace on before running the example and then post the output just before the error occurs? Could y...

It may be that the trial wrapper isn't passing on the command to MLwiN. You can test this with the command option "mlwin /help". If it doesn't display a list of possible options then this is the case. An alternative way to reset the size is to copy the following into a text file called &qu...