C
chatterbox
Hello Everybody - No its not Dr. Nick
I am a relative newcomer to programming and to vba, but I run fast
.
I have distributed a prototype vba project for Excel amongst colleagues
and the feedback has been good, so much so that there has been a
request to broaden the user group. We would like to protect the project
integrity, and so we are thinking of moving beyond vba for security
reasons (I read about it in a book), but still wish to retain Excel as
the main user interface. If I ask people, one says we should use VB6,
another suggests VB.Net, and another might suggest C#. I have read
books and articles and am none the wiser. Could someone offer any
clear water and put me out of their misery ?
To give a little flesh to the project, it is a form based application
where the user enters information, along with information they have on
worksheets. The information is processed and the output is sent back to
a worksheet, the user's normal working environment. The forms merely
facilitate what can be a tricky operation, but some of the processing
can be quite mathsy. Feedback from the group suggests we might also
(later) store historical results to an Access database.
Any advice about which way to proceed would be appreciated.
Ciao.
chatterbox
I am a relative newcomer to programming and to vba, but I run fast
.I have distributed a prototype vba project for Excel amongst colleagues
and the feedback has been good, so much so that there has been a
request to broaden the user group. We would like to protect the project
integrity, and so we are thinking of moving beyond vba for security
reasons (I read about it in a book), but still wish to retain Excel as
the main user interface. If I ask people, one says we should use VB6,
another suggests VB.Net, and another might suggest C#. I have read
books and articles and am none the wiser. Could someone offer any
clear water and put me out of their misery ?
To give a little flesh to the project, it is a form based application
where the user enters information, along with information they have on
worksheets. The information is processed and the output is sent back to
a worksheet, the user's normal working environment. The forms merely
facilitate what can be a tricky operation, but some of the processing
can be quite mathsy. Feedback from the group suggests we might also
(later) store historical results to an Access database.
Any advice about which way to proceed would be appreciated.
Ciao.
chatterbox