I have a connection in my database pointing to an ODBC connection to an Access database. I also have several remote views that use this connection. When I run the program I get a "connection is busy" error. Using the ConnectBusy attribute of the SQLGETPROP function, I put a DO WHILE construct in the code to display a message detailing the step that the program is at for as long as the connection is busy. This shows that the connect is always busy. However if I put a SET STEP ON after the remote views are "USED" and before the queries that modify the tables are called, I can step through the program without any problems. If I SET STEP ON at the begining of the program and immediately select resume, it sticks. If I step through the program, it works. Any ideas?