C# Add-in vs VBA Macro for Excel functionality -
we give users of our system opportunity drag of data database excel. (only reading data, no chance of writing data db). users not have direct access database, have authentication them in place. (firstly connect database, secondly use security settings of our system, user 1 allowed see tables.)
i instructed begin writing c# addin this, colleague instructed write vba macro.
i thinking of using entity framework access data, haven't worked before. don't know using within macro, macro-manager thinks killing network heavy data transfer. doesn't idea users have install add-in on computers. however, have vague uneasiness regarding macro's , notion they're not secure. how safe macro's? tweak-safe, or knowledgable user change code?
i know, pro's , con's of each approach , general feeling of people more experience , knowledge myself?
with particular regard matters such as:
- information security (some tables should not accessed.)
- network traffic
- ease of maintenance , future modifications
- any other relevant concern i've missed
kind regards,
what in situation is: -create views on database , assign them schema. don't restrict data, specify columns want them see, let them filter data in excel (assuming it's massive amount of data returned) -create active directory group , give members of read access schema -use excel -> data -> connections (it's in excel 2010, not sure 2008) connect worksheets view
they can mess away data in excel, can't written database. , can restrict tables / columns can see, , joins lookup tables in view don't see database ids.
Comments
Post a Comment