Saving the odbc connect string - tag or table?

[ragtopcaddy via AccessMonster.com]

I have a fairly static odbc connect string that should be visible in a text
box on a form for reference purposes. It seems excessive to me to keep a
table with 1 field and 1 record to record this string. Is it advisable to use
a tag instead? I'm thinking of keeping the string in the textbox's tag, and
providing a cmd button to change the value in the tag and updating the
textbox value, on those rare occasions when it might be required.

Thanks,

--
Bill Reed

"If you can't laugh at yourself, laugh at somebody else"

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200711/1

[Technolust]

On Nov 19, 8:54 am, "ragtopcaddy via AccessMonster.com" <u9289@uwe>
wrote:

I have a fairly static odbc connect string that should be visible in a text
box on a form for reference purposes. It seems excessive to me to keep a
table with 1 field and 1 record to record this string. Is it advisable to use
a tag instead? I'm thinking of keeping the string in the textbox's tag, and
providing a cmd button to change the value in the tag and updating the
textbox value, on those rare occasions when it might be required.

Thanks,

--
Bill Reed

"If you can't laugh at yourself, laugh at somebody else"

Message posted via AccessMonster.comhttp://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/2007...

One thing you could do is store the value in an .ini file. When you
retrieve the value, store it in a public variable.