Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hi,
This is just question about good practices... I would like to save settings that accompany an add-in that formats structured text files into useful spreadsheets. There are essentially 3 short lists that need to be stored, 1 list of names and 2 lists of bools. They are wiped and recreated when settings need to be changed. They only need to be accessed by the add-in. On every thread and website I've looked at, it's recommended using .ini files or the registry. I found it was very easy to simply use 3 vba-named sheets in the add-in, and reference the values by the sheetname.cells(index). There is a settings macro that stores the new settings when required using inputboxes and msgboxes and saves them using thisworkbook.save. Is there any reason why this would be dangerous or considered bad practice? (I realise a nice dialog would be better for the input, but the settings would be changed only once every couple of years or so, if at all, and only 4 or 5 input boxes and 8 or 10 msgboxes would need to be negotiated with.) Thanks, Michael Lodge |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Where do excel 2003 add-in's live? | Excel Discussion (Misc queries) | |||
COM add-in's | Excel Discussion (Misc queries) | |||
Location of Add-in's | Excel Programming | |||
Office 2003 Purchaser can't add in the add in's. Why? | Excel Worksheet Functions | |||
Protecting Add-In's from viewing | Excel Programming |