We are in the process of upgrading a MS-Access(97) database to SQL Server 2000. We will still be using an Access front-end program to access the SQL backend. I have used DTS to import the data into SQL and have linked the data using ODBC. The data looks fine but I have 2 questions.
Question 1 - The current program has a function which displays the user table on the screen, so that managers can input new user data along with their passwords. The Access table is using a "password" input mask to prevent echoing the password back to the user. After I converted the database to SQL the same Access code displays the same information on the screen but all of the user passwords are visible. Is there anyway to prevent this? I thought of simply using a view but they still want to enter passwords on the screen.
Question 2 - The current appl is using the MS Access autonumber functionality. I modified these fields to use identities but now the Access appl will not give the users the >* function (to add new rows to the table).
Sorry for such a long post and thanks in advance for any sugestions.
Sunny
Question 1 - The current program has a function which displays the user table on the screen, so that managers can input new user data along with their passwords. The Access table is using a "password" input mask to prevent echoing the password back to the user. After I converted the database to SQL the same Access code displays the same information on the screen but all of the user passwords are visible. Is there anyway to prevent this? I thought of simply using a view but they still want to enter passwords on the screen.
Question 2 - The current appl is using the MS Access autonumber functionality. I modified these fields to use identities but now the Access appl will not give the users the >* function (to add new rows to the table).
Sorry for such a long post and thanks in advance for any sugestions.
Sunny
