Why doesn't my > button work?

[elizabeth]

I used to be able to open some code, click on a sub, click on the <b>[<font color=red>&gt;</b></font> button (&quot;Run Sub/User Form&quot on the Debug toolbar, and it would run my code. These days it pops up a Macro dialog box instead. I don't remember if this started when I began using version 20000. What's up?

 

[RoyVidar]

I'm not sure either, whether this is an A2K spesific thing, but found some occasions where the Macro-thingie pops up. Don't now if its helpfull, but...<br><br>I've found it not available from a form using timer, at least those events I'm triggering. <br><br>Whenever your cursor isn't placed in the actual code you wan't to run, for instance in a module header etc.<br><br>It seems to me that whatever action isn't available from the state the form is in at the time one want's to run code, determines whether you're allowed to run it or not.<br><br>Are there any others finding this a bit annoying?<br><br>Roy-Vidar

 

[DiscoDuane]

I've run across the same thing<br>

 

[Geekette]

i think it's an &quot;improvement&quot; of a2k. in theory, (i believe a microsoftie told me this @ tech meeting) macro code that didn't &quot;convert&quot; to a2k's <font color=red><i>high vba standards </font></i>would be singled out. in other words, did this error happen on a vba script or macro that you originally wrote in access97 (or earlier)?<br><br>i've gotten this annoyance in such instances. i use (or used to use) macros a lot, because i am 1) lazy and 2) no vba guru. <br><br>a2k is forcing me to use vba more and more. the downside is that vba still isn't vb, so sometimes stuff written in vb (i'm teaching myself visual basic) doesn't quite work in a2k.

 

[elizabeth]

Geekette, the problem is not related to a macro in my case. The macroname select box is empty, and anyway I have never written a macro in this database. I avoided bothering to even learn about macros because in my first Access class I was told VBA is superior in every instance except the 2 or 3 functions that VBA can't handle. I did kluge together a couple of macros a couple of years ago for some kind of import function and something that required sendkeys. <br><br>BTW, there's a white paper from MS listed on the FAQ page of this forum (under &quot;Version or Conversion Related) that gives examples of converting DAO to ADO, if that is what your conversion problem is.