TheSwamp

Code Red => VB(A) => Topic started by: BlackBox on December 01, 2011, 01:46:57 PM

Title: Microstation VBA
Post by: BlackBox on December 01, 2011, 01:46:57 PM
I feel like a noob all over again... Would someone please point me in the right direction of a good VBA reference, specific to Microstation V8(i) (if possible)?
Title: Re: Microstation VBA
Post by: Matt__W on December 01, 2011, 01:48:07 PM
http://communities.bentley.com/products/microstation/w/microstation__wiki/microstation-v8-vba-programming-resources-cs.aspx


Microstation really like's itself judging by the linky above.
Title: Re: Microstation VBA
Post by: BlackBox on December 01, 2011, 01:52:17 PM
Thanks for the prompt response - I'll give the hyperlink a look-see. :beer:

Microstation really like's itself judging by the linky above.

... You have no idea, how much I dread working with this outdated, half-wit State DoT customized, malarkey. *sigh*

Title: Re: Microstation VBA
Post by: MP on December 01, 2011, 01:55:56 PM
Microstation really like's itself judging by the linky above.

(http://i43.tinypic.com/357gj75.jpg)
Title: Re: Microstation VBA
Post by: BlackBox on December 01, 2011, 02:11:25 PM
Microstation really like's itself judging by the linky above.

I'm not sure if it's just the folks in my office, or what, but seemingly that essence rubs off on the veteran users too... They don't know what VBA stands for, and cannot possibly understand why I would need to use anything other than what the State DoT has provided us.  :roll:

How 'bout... 'Cause I can do it better? 

Ummm... Well... You know, once I learn the Microstation Object Model, etc. :lol: LoL
Title: Re: Microstation VBA
Post by: alanjt on December 01, 2011, 02:32:38 PM
Microstation really like's itself judging by the linky above.

(http://i43.tinypic.com/357gj75.jpg)
That picture will haunt my dreams.
Title: Re: Microstation VBA
Post by: BlackBox on December 01, 2011, 02:35:16 PM
That picture will haunt my dreams.

What exactly is "haunting"... Microstation, or what you look like?  :-P
Title: Re: Microstation VBA
Post by: Matt__W on December 01, 2011, 02:41:12 PM
That picture will haunt my dreams.
Oh really?  Well then what about......




THIS??!?
Title: Re: Microstation VBA
Post by: MP on December 01, 2011, 02:43:01 PM
Deodorant.
Deodorant.
Deodorant.
Title: Re: Microstation VBA
Post by: alanjt on December 01, 2011, 02:44:19 PM
(http://www.theswamp.org/lilly_pond/alanjt/uglyToLookAt.gif)

There are things I have seen that cannot be unseen.
Title: Re: Microstation VBA
Post by: Keith™ on December 07, 2011, 06:46:33 PM
I have the V8 VBA reference chm file along with the API and MDL references. If you would like them let me know.
Title: Re: Microstation VBA
Post by: BlackBox on December 07, 2011, 07:06:35 PM
I have the V8 VBA reference chm file along with the API and MDL references. If you would like them let me know.

Thanks Keith!

I only have V8i installed, and did get IT to install the V8i MDL SDK as well. My problem is, that I have been unable to find a single example of a VBA Module that interacts with the CadInputQueue Object, using the GetInput Method with various MsdCadInputTypes, etc..

Every example that is included in the V8i MicrostationVBA.chm that supplies a point to a function is hard-coded (meaning the VBA code supplies the X,Y,Z) - How does one even do something as simple as prompt the user for MbePoint, or Point3D (if you know)?

I'm finding the development documentation, similar to the platform in general... Cumbersome, difficult to work with, and necessary to jump through additional "hoops" for the same (if not similar) result.
Title: Re: Microstation VBA
Post by: Keith™ on December 07, 2011, 07:35:25 PM
I'd have to reinstall it to look at the code that I wrote some time ago, I don't even remember if the code actually did anything or if it was just a loader for the VB class I was using.

You are welcome to take a look at it if you want.
Title: Re: Microstation VBA
Post by: BlackBox on December 08, 2011, 01:09:17 AM
I certainly don't mean to cause you undue effort, but if you're willing to provide me that sample, I'd really appreciate it.
Title: Re: Microstation VBA
Post by: Keith™ on December 08, 2011, 02:01:04 PM
Here is the stuff I have. I am still trying to find the actual code, but I'm not having any luck.
Title: Re: Microstation VBA
Post by: BlackBox on December 08, 2011, 03:56:30 PM
Here is the stuff I have. I am still trying to find the actual code, but I'm not having any luck.

Thanks Keith; I'll be able to look it over later this / next week.

Greatly appreciated - Cheers! :beer:
Title: Re: Microstation VBA
Post by: BlackBox on December 09, 2011, 09:22:24 PM
I'll be able to look it over later this / next week.

I might not get the chance to even take a look at this... It appears that my job is in jeopardy (unexpectedly).


Title: Re: Microstation VBA
Post by: Keith™ on December 10, 2011, 12:04:55 AM
ouch .. that sucks
Title: Re: Microstation VBA
Post by: Jeff H on December 10, 2011, 03:50:53 PM
Sorry to hear that and hang in there.
Hope it all works out for the best.
 
Title: Re: Microstation VBA
Post by: BlackBox on December 10, 2011, 07:38:14 PM
Thanks guys. :beer:

I wish I could say that it is just one of those things, the economy, downsizing, etc. but it's not.

I've felt for some months now that there's something afoot. That suspicion was realized when my former boss was laid off, and there began a solid push for a unified CAD platform shift to Microstation from a dual platform group.

I'm asked to start working in Microstation late October, and just last week was unexpectedly taken off of the project due to my lack of production. Never mind that since starting to work with Microstation I've received less than a day's worth of training... 5 mins here, 30 mins there. I was given a web URL for some State training PDF's and left with the statement "the PDF's are your friend."

No training plan was developed let alone implemented, and the same person appointed responsible for our training was also responsible for assessing my proficiency. Not once was I pulled to the side so to speak for my proficiency. This same guy passed on additional tasks to me because he "didn't want to get in trouble for tasking [his] wife" whom also works under him from home part-time and is very adept at Microstation (8-10 yrs)... Conflict of interest much?

I'm beginning to suspect that this guy was getting in trouble for the submittal potentially being late (he's the Sr. Designer for this project), and hasn't been keeping the Project Manager aware of our real status. Then when light is shined on reality as a result of my emailing them both stating that "I need help" that a serious look was given to the project and I am the fall-guy for his CYA action plan.

I have five years of flawless reviews, and several unsolicited laudatory statements. Some that went all the way up the chain, two of which came from this same guy is burning me now. Well if I'm lauded for my proficiency with AutoCAD, and I work with Microstation for the first time I've ever opened the program, and only worked with it for a month or so (I did work on some other AutoCAD projects in there too), the what's different? It ain't me.

Sure there's a learning curve to consider on my part, but if you give me little training, and never. Other to pull me aside for corrective discussion / action, then how is it that I am responsible for this failure? Rhetorically speaking.  *Shrug*

Aside from an attempt to defend / redeem myself come Monday (we're having a meeting to clear the air from the horses mouth), I clearly need to find another group to work with, or even a new employer altogether. My last review was +/-10 days ago, and it was flawless. I'm not sure what else to do at this point.

Anyone have any suggestions? I already work for the largest firm in my area, so I'm open to relocation for the right fit.

** Edit - I should have mentioned that I live in SW Florida currently.

I'm at a loss here, and still don't know what to make of this... Whatever concerns they have of me have not yet been communicated to me. My supervisor asked me some questions and was visibly bothered by the "conflicting information" so I'm planning to go through all of my email, and IMs to disapprove what I can. See how it plays out from there. What else can I do at this point.
Title: Re: Microstation VBA
Post by: Matt__W on December 12, 2011, 08:35:16 AM
Anyone have any suggestions?
Leave the shotgun at home.


But in all seriousness... I hope things work out for you.  It's definitely a "slightly" uncomfortable situation to be in.  It's sort of like when daddy smacks mommy at the dinner table.  Well, maybe not EXACTLY like that....
Title: Re: Microstation VBA
Post by: BlackBox on December 12, 2011, 09:46:53 AM
But in all seriousness... I hope things work out for you.  It's definitely a "slightly" uncomfortable situation to be in.

Thanks, Matt.

I did the only thing I felt that I could do at this point; I went through all of the communications I have (i.e., IM, Email, etc.), and I printed them, highlighting critical bits like when I was tasked with something, the feedback received when I provided my weekly status updates (i.e., copied my file(s) to them), and was able to show that at no time was anything derogatory mentioned to me about my productivity. I also went through the design files, and created a spreadsheet of time worked on each, in addition to a breakdown of the time billed to the job (i.e., how much time for travel, training (or the lack thereof), and billable time).

I brought the 2" binder's worth of documentation into my boss this morning, and explained that I am confused, I do not even understand what it is that I am being accused of, or by whom, and that here's the details of what I have (the printouts), but then I noted that I pulled out what I felt were the critical bits, and that more can be provided at his request. I made it clear (as the documentation validates) that all of my activities went through the Sr. Designer as instructed by the Project Manager. My inefficiency in Microstation is not due to negligence, but a lack of training and experience - I have six years of AutoCAD. I explained that at this point I am at a loss for what I could have done to jeopardize my job security - but would like to readily address and and all concerns.

Now I wait to see what comes from all of this.  :?
Title: Re: Microstation VBA
Post by: BlackBox on December 14, 2011, 02:23:18 PM
<snip>
Title: Re: Microstation VBA
Post by: BlackBox on December 14, 2011, 02:25:50 PM
Oh! And we just got an email (my Fiance and I) today during lunch that our short sale offer was accepted today; we have a mandatory 30 day close... Looks like I'm moving over the holidays!  :lmao:
Title: Re: Microstation VBA
Post by: MP on December 14, 2011, 02:57:30 PM
Since this thread is almost fully derailed ...

So sorry to hear of your shďtuation -- I genuinely hope the new year brings much better opportunities for you to use and develep your many skills, and all due acknowlement by your employer(s).

But if I could be completely candid -- I think you're being too candid -- might reconsider what you're publishing to the world.

/conscience clear
Title: Re: Microstation VBA
Post by: alanjt on December 14, 2011, 02:59:01 PM
might reconsider what you're publishing to the world.
*Mark runs off to sign over all content to Google and Facebook*
Title: Re: Microstation VBA
Post by: BlackBox on December 14, 2011, 04:05:47 PM
Since this thread is almost fully derailed ...

So sorry to hear of your shďtuation -- I genuinely hope the new year brings much better opportunities for you to use and develep your many skills, and all due acknowlement by your employer(s).

But if I could be completely candid -- I think you're being too candid -- might reconsider what you're publishing to the world.

/conscience clear

Thanks, Mike... Dually noted.
Title: Re: Microstation VBA
Post by: Keith™ on December 14, 2011, 05:43:10 PM
Wouldn't you know it .. the software I was porting to Microstation some years ago that never got traction because of lack of interest has suddenly gotten alot of interest ... I might be digging up this old bit of code and porting it after all ...
Title: Re: Microstation VBA
Post by: caddcop on December 20, 2011, 07:52:53 AM
In an attempt to put this cart back on track...
In closing, I have come from the other direction - learned the original mainframe IGDS before MicroStation but now can use both AutoCAD and MicroStation. Which do I prefer? MicroStation. But there are some features of AutoCAD that are better than MicroStation. However, there reverse is also true. Thankfully, their interfaces are becoming more and more alike over time.
MicroStation also supports keying in a number of AutoCAD commands. Type DWG followed by an AutoCAD command and see what happens. Actually, DW is all you must type, as when typing in commands, MicroStation auto-completes them as soon as it sees a match in its command lists. There is also a shortcut key \ or / - I can never remember which that can be used instead of DWG, but I have not had good success with it - so I stick to DWG.
And never underestimate the skill set of being dual cad literate.
Title: Re: Microstation VBA
Post by: BlackBox on December 20, 2011, 07:56:46 AM
Thanks for your response, caddcop.

/cart off track