All of the functions you can use in VBAI can be found in the Vision palette within LabVIEW.
I don't have Vision installed anymore but a quick search through that palette will probably help you.
Brad, are you an expert on VBAI by any chance?
I worked on a project last year where I couldn't get the IMAQ outputs to match what I was seeing in VBAI (this was some OCR stuff I believe coupled with a few image operations). I even generated LabVIEW code from VBAI and copied the exact IMAQ VIs from there in the same order and it still didn't come out the same. Is this something you've observed before? It doesn't really matter anymore as I moved companies, but in the end I had to use the generated code all on its own without alteration, which I don't like to do because then a new developer has to use VBAI to change anything.
Brad, thanks for the response. I don't have access to the code anymore, I was more just curious about it. One of my old coworkers has actualy been in contact with me recently because he's the one who inherited my code. I had to walk him through how I implemented the VBAI code in to the main application because he couldn't just change a few setting inputs. It was more of just a inconvenience.
I guess my suggestion for the future would be for an option to output the VBAI code as LabVIEW code without all of the subVI hierarchy for those who are used to just using the IMAQ VIs. Just a linear set of code that goes from the start to fnish of the VBAI diagram that I could manipulate the way I want would be nice.