I haven't made the .ini switch yet. It seems like a good idea and seems to be generally accepted as the way to go.
But everytime I look at the instructions, I get confused. It is probably pretty straight forward- but the instructions link to another script which then tells you to load another script....
I really don't want to load a bunch of scripts that I am not currently using just to get .ini to work.
The information is just too scattered.
I would be great if some simple "step by step" instruction with just the basic components of the .ini system could be posted. It would also be nice if the basic components were all in the same place.
Some instructions for coders would also be helpful.
Another question in regard to the .ini- it seems to use the Access .mdb format. Does Access need to be installed on the HS computer. I can install it but only if necessary.
Thanks
But everytime I look at the instructions, I get confused. It is probably pretty straight forward- but the instructions link to another script which then tells you to load another script....
I really don't want to load a bunch of scripts that I am not currently using just to get .ini to work.
The information is just too scattered.
I would be great if some simple "step by step" instruction with just the basic components of the .ini system could be posted. It would also be nice if the basic components were all in the same place.
Some instructions for coders would also be helpful.
Another question in regard to the .ini- it seems to use the Access .mdb format. Does Access need to be installed on the HS computer. I can install it but only if necessary.
Thanks
Comment