I'm trying out the ElevateDB 2 .Net data provider using Visual Studio 2005. When
connecting local mode, the data provider does not appear to be cleaning up temporary
files. The problem goes away when I use the same code in remote mode.

Hilary,

<< I'm trying out the ElevateDB 2 .Net data provider using Visual Studio
2005. When connecting local mode, the data provider does not appear to be
cleaning up temporary files. The problem goes away when I use the same code
in remote mode. >>

What is the code that you're using ?  You need to make sure to use the
Dispose method on all EDB object instances or else the resources won't be
cleaned up properly.

--
Tim Young
Elevate Software
www.elevatesoft.com

Here's the code that I am using:

   Dim cnEDB As EDBConnection = New EDBConnection(ConnectionString)
   Try
     Dim cmdEDB As EDBCommand = New EDBCommand("SELECT Link FROM DailyDevelopmentTips
WHERE TipID=1", cnEDB)
     Try
       cnEDB.Open()
       Dim drEDB As EDBDataReader = cmdEDB.ExecuteReader()
       Try
         If drEDB.Read() Then
           Return drEDB.GetString(0)
         End If
       Finally
         drEDB.Close()
         drEDB.Dispose()
       End Try
     Finally
       cmdEDB.Dispose()
     End Try
   Finally
     cnEDB.Close()
     cnEDB.Dispose()
   End Try

Hilary,

<< Here's the code that I am using: >>

Thanks.  I found the issue yesterday - there is a problem with any .NET
version of ElevateDB and delete/rename.  The compiler directives for the
..NET products are messed up in a way so as to not cause an error, but to
eliminate the delete/rename code so that they don't do anything.  A fix will
be in the next 2.01 release, which should be available by the middle of the
week.

--
Tim Young
Elevate Software
www.elevatesoft.com