Want to learn VBA for Microstation, Online Coarse or book, or VB scripting.

Actually, there are onDemand eLearning courses for MicroStation VBA -- those can be found starting on http://www.bentley.com/en-US/Training/Products/Resources/Books/

More details on the "Learning MicroStation VBA" Bentley Institute book mentioned can be found on http://www.bentley.com/en-US/Training/Products/Resources/Books/Learning+MicroStation+VBA.htm

Unknown said:

I followed all the instructions in Chapter 5, Modules, Forms and Class Modules. I discovered that there are some steps left out in his instruction or else he did not properly review this part.

I am not only new to Microstation vba but also vba in general. I agree, is difficult to follow the book. I did manage to get chapter 5 to work with the class module. First off I did not have my class module named clsTarget as the instructions said. Second, on page 53 the screenshot does not match the code listed at the bottom of the page at the part where it reads "And here is the code as it should be typed:" eventhough they are supposed to be the same. My code did not match the screenchot(which is correct) I typed my code to match the bottom of the page. The difference between the codes is the first line after the "Public" statements:

Sub Draw(X as Double, Y as Double, Z as Double)

The screenshot just shows Sub Draw()

After removing the "Double" statements the program ran fine. I pulled my hair out trying to figure this out!

I am currently using Microsoft's site for a learning vba tutorial for a better understanding of vba before moving forward with Microstation vba.

Bliksem,

I have to agree with you. For a $90 book to have mistakes like this is unconscionable. It is difficult enough to learn a new programming language without having to fight with code that obviously has not been proofread. I looked online for a least an errata sheet but apparently none exists. Bentley is obviously aware that this book has errors. Come on Bentley, how about a simple errata sheet?

Jonathan Martin said:

Come on Bentley, how about a simple errata sheet?

If you have any specific for instances, we will certainly look into them. TIA

Let me start with two in Chapter 5 that would be helpful,

First, as Bliksem mentioned, the code on page 53 (towards the bottom of the page) has:

Sub Draw (X As Double, Y As Double, Z As Double)

That code will cause the program to fail. The correct code should be:

Sub Draw()

If you'll notice, the screen shot on the same page has the correct code.

Another thing that would be useful (particularly to new programmers) is if somewhere in the text it mentions that the coding in Chapter 5 should be done using the design file called "Nothing.dgn." I started entering code using one of my blank design files and couldn't get the code to work. After just a bit of snooping, it occurred to me that the call to "nothing" wasn't a VBA call or variable, it was just the name of the design file. Might be nice if Jerry had mentioned that somewhere.

I'll post any other problems as I come to them. I'm going to let the typos side (at least three in Chapter 5 and 6) because, after all, it is a technical book and grammar has no place in technology.

Got another one for you that I ran into today.

In Chapter 10 we start in with the user interface on Page 167. A new form is created, a bunch code is added. You get to page 173 and a three line code is added which starts up the form. The code is:

Sub DoCellInsertion()

  frmCellInsertion.Show vbModeless

End Sub

Great. The problem is, no where did it say to rename the form to "frmCellInsertion". So, if you are new to VB and you see that call, you probably aren't going to realize that it is calling the form by its name. It should be mentioned on page 168 when you are building the form that the name of the form needs to be changed.

Got another one for you that I ran into today.

In Chapter 10 we start in with the user interface on Page 167. A new form is created, a bunch code is added. You get to page 173 and a three line code is added which starts up the form. The code is:

Sub DoCellInsertion()

  frmCellInsertion.Show vbModeless

End Sub

Great. The problem is, no where did it say to rename the form to "frmCellInsertion". So, if you are new to VB and you see that call, you probably aren't going to realize that it is calling the form by its name. It should be mentioned on page 168 when you are building the form that the name of the form needs to be changed.

I should get paid for this.

Page 174, the Point List Reader. Thing is, it doesn't seem to work. Not by keying the code from the book or running the code from the CD.

In the subroutine btnRead, the debugger doesn't seem to like the line:

Open txtPointFile.Text For Input As #FFile

Soooo... I'll try to brute force this one to figure out why it doesn't work, but, you know, an errata sheet... just sayin

Thanks... we will look into these things.

Well the three lines of code that are relevant here would be:

Dim FFile As Long ' declare a variable to hold a long integer

FFile = FreeFile ' VBA function FreeFile gets the next available file number

Open "fileName" For Input As #FFile ' open a text file of name "fileName" to read in and use file number FFile

This is common VBA code.  If you tried to put #FFile in the debugger it would be a problem.  What is the value of FFile after the assignment from FreeFile?

HTH,

Mark,

Thanks for the response. I suppose to find the value of FFile, you'd have to use the Watch Window. Unfortunately, I haven't gotten to that chapter yet, I'm only to chapter 14. But, when I do get a bit further along, I'll revisit this code to see if I can work through it. But, in the meantime, you might want to take a look at the book (Learning MicroStation VBA) and eyeball the code for the Point List Reader on page 174. The code in the book and the CD doesn't appear to work... not for me anyway.

Regards,

Jon