I have been programing for 20 years in assembly, and several propriatary 'basic like' langages. I need to re-write my software into Microsoft Windows using Visual C++ and MFC (I think)... I have a pile of books and am as lost as the day I started trying to learn this #@$!#%! Can anyone out there communicate with me and give me some direction...I am very, very, confused and stuck!
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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
HELP ME!!! 1
- Thread starter mwr412
- Start date
-
1
- #2
programsecrets
Programmer
As long as you do your part, we're here to help. Take it slow (one topic at a time) and very briefly describe what you understand and then ask one or two specific questions so we can try to help you.
Incidentally, it only *seems* to be "#@$!#%!". It's not that at all once you know more about it. X-)
Incidentally, it only *seems* to be "#@$!#%!". It's not that at all once you know more about it. X-)
- Thread starter
- #3
Ok, Here's where I'am at...I am attempting to re-write my accouting software (developed in DOS over a 15 year period) into a windows enviroment. First question...should I use MFC or not? And why? Bear in mind this is not a simple program I am developing...it is a very robust and highly specialize accouting and managemnt system for a very specific industry. To give you a better idea of how serious this app is...the orignal DOS program sold for 4k-6k per installation!
programsecrets
Programmer
-> ...should I use MFC or not? And why?
Looks like one of your priorities is to make programming as simple as possible. MFC simplifies programming compared to programming using only the Win32 API. On the other hand, MFC does have a learning curve, but once you've mastered some things, others start to become intuitive.
MFC increases the size of your executable and/or the size of the libraries your program must load upon initialization. Most of the time, that's not a big deal, unless you're developing for internet, where people must download your (large) program and/or it's libraries, or if your application must run on PCs with limited memory (which is not much of a problem anymore).
As an alternative, you could divide your application into two parts:
1) Graphic User Interface (GUI), written using Visual Basic
2) Business logic portion (including processing and database interaction), written in C++ as a DLL library.
This could lower your learning curve, since VB GUI programming is much easier than Visual C++ GUI.
Then, you could concentrate on using C++ (with or without MFC) for just the non-GUI buisiness logic.
Looks like one of your priorities is to make programming as simple as possible. MFC simplifies programming compared to programming using only the Win32 API. On the other hand, MFC does have a learning curve, but once you've mastered some things, others start to become intuitive.
MFC increases the size of your executable and/or the size of the libraries your program must load upon initialization. Most of the time, that's not a big deal, unless you're developing for internet, where people must download your (large) program and/or it's libraries, or if your application must run on PCs with limited memory (which is not much of a problem anymore).
As an alternative, you could divide your application into two parts:
1) Graphic User Interface (GUI), written using Visual Basic
2) Business logic portion (including processing and database interaction), written in C++ as a DLL library.
This could lower your learning curve, since VB GUI programming is much easier than Visual C++ GUI.
Then, you could concentrate on using C++ (with or without MFC) for just the non-GUI buisiness logic.
- Status