On Tue, 5 Jan 2010 15:26:32 -0500, "JLGWhiz" wrote:

The error 400 occurs when you try to open a UserForm that is already loaded
and displayed. So, if you are getting that error when you open workbook,
you need to check the ThisWorkbook code module to see if there is a
Workbook_Open event code that is calling a UserForm that might already be
open. If not, then you need to try and isolate the cause that initiates the
error and report it for a possible bug in the 2010 beta version.



No, I am certain that it is in my macro script.

Thanks. I need to trap for the condition of the workbook, and act
accordingly. Thanks again.


"CellShocked" <cellshocked@thecellvalueattheendofthespreadsheet. org wrote
in message ...

Is there a standard command in a macro that will move one to the bottom
of a range?

The row count varies, and I always want to get to the bottom, and
recording a macro doesn't work as it uses direct references.

Also, for some reason, ever since I opened this workbook in 2010 beta,
I get a 400 error in my sheet manipulation routine. It never happened in
2007, but now even happens in that release. Did opening change something
about the workbook that I do not know about?

It used to work fine.

I do think that I have a very recent, pre-2010 backup, however. I
haven't tried to see if that one does it as well. If it does, does that
make it a registry problem, since my 2010 install was told to keep the
current version intact? Both are 32 bit. The 2007 is pro, and the 2010
is a beta offering I DLd from MS.