Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VB.NET samples. Help Prog Newbie. 3

Status
Not open for further replies.

AlexJhb

MIS
Dec 13, 2001
90
ZA
Hi,
Very new to programming. Accpac QI.
Want to replace VBA macros with VB.NET as I need more features and screens in particular. Understand that VBA has limitations.
Tried Delphi but could not get the API to work. No documentation that I could find. (I was doing some work with Delphi at the time, about two months ago)
Printed the SDK manuals but had to be saved from the madhouse. Decided that was for BSc propellerheads.
So ended up with VB.NET as in VS 2003.
Spent 3 weeks going through a MS VB.NET book and I think it will do what I want. (I am sure it can and I am keen to try). To start I cannot get the DOT NET example in the SDK tutorial to work and the statements in the help are different. Complains about type not defined in the (Dim) definition sections.
So tried working from the existing macro side by just leaving out the ADO stuff and also just a simple recording. But still too much of a dummy to get things working.
Questions
1. Is VB.NET the way to go? Don't say C# because I have no experience there and have not done Visual C++, only a bit of C++ (DOS level 1st year university stuff). Looks like Delphi is not used much and you need to know enough to figure out the API. If you say Visual C++, I expect I can take time to do that but was hoping to do atv least 3 macro conversions before year end.
2. If VB.NET is acceptable, then where can I find more info to get started? Even a few examples. (saw one on this forum I will try)
Seems Jay has not done that book yet. Not sure if Ettienne has either.
(For Ettienne: Kom ouboet, help 'n ou Transvaaler asb.)
 
I don't use VB.NET because it's overkill. VB6 is plenty for Accpac.

If your types aren't defined, sounds like you just need to add a Reference to the Accpac COMAPI to the project.


Jay Converse
IT Director
Systemlink, Inc.
 
Tks for your reply.
Yes, I thought that may be the case. A friend advised that in general it was maybe better to learn VB.NET directly so I can use it for other projects as well because to learn VB6 and then VB.NET, according to him, is too much of a shift. Would you advise that I go back and learn VB6? Maybe it is not too much different from VBA?

OK, I discovered my problem with the sample code was that I did not have the Accpac .NET stuff loaded and referenced. Had to reload SM to get this sorted. The code looks very different for Accpac and VBA. Do you know if there is any advantage in using the .NET Accpac coding, like speed or something? Or is Accpac just going that route because MS says so?

Maybe it is better to just use the COMAPI in .NET so that the code is similar to the macros? On the Accpac side anyway. That way I can stay on track with one language.

Again it seems no documentation on the Accpac .NET code and you need to be an experienced programmer to use that, which I am certainly not.

I am willing to struggle a bit if it means there is a long term advantage. An advantage would be if Accpac is moving strongly towards .NET and/or there are speed or feature advantages. If not, maybe I should reset the clock and go back to VB6 for Accpac and Delphi for everything else.

Would appreciate some advice Jay so that I can stop going around in circles.

Appreciate your help so far.
 
Ja Kleinboet, bly met VB6.
I use VB6 with all my Accpac devs, it is simple and easy and does what I need it to do. I looked at VB.Net and decided to stay on the VB6 wagon until the trail ends. (But then it took me a while to move from VB3 to VB6.) I do not believe there is any advantage at this point to move to VB.Net for normal devs - unless you are in an environment where .Net is really required. There is no reason to work in C# or C++ either unless you are into SDK stuff.
 
I second Ettiene's motion. VB.Net is just another way for Bill Gates to make money. There are absolutely _no_ speed or feature advantages.

Jay Converse
IT Director
Systemlink, Inc.
 
Well this is good advice from two Pro's.

Appreciate your advice.

Will have to find if I can still source VB6. Have some books on it, so have a start. Must say I am relieved. Was not sure where I was going was the right choice.

Thanks once again.

 
eBay is full of VB6, just don't know about international shipping if you are not in the US. You can also try Amazon, sometimes they have old copies of stuff.
 
No VB6 available anywhere here in South Africa. Found a copy on an old MSDE set but no CD. MS no longer supply backups. After 2 weeks found someone with a CD. Seems to work with SP6 loaded.

Thanks to all.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top