I think I figured it out, I will have to try it at there site tonight to test it out.

In my script, I was adding the I was using the wrong syntax for adding a key.
I then read in my book that I don't have to use the "ADDKEY" function, I could simply just use the "writevalue" function and it will add the key as well as the value. Once I straightend everything out with my test script in my testing enviroment,upon login it added the .txt ODBC connection.

Here is a portion of my script that I am using for my live enviroment:

WriteValue ("HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources","SmartClinic", "SQL Server","Reg_SZ")
WriteValue ("HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\SmartClinic","Driver", "C:\WINDOWS\system32\SQLSRV32.dll","REG_SZ")
WriteValue ("HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\SmartClinic","Description" "SmartClinic","REG_SZ")
WriteValue ("HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\SmartClinic","Server", "MEDICALSERVER","REG_SZ")
WriteValue ("HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\SmartClinic","LastUser", "sa","REG_SZ")

I will test it and let you guys know how it worked:

Thanks again