oledb

I currently have a 32-bit PowerBuilder application that we are trying to port over to a Windows 7 64-bit environment. Realizing the obvious that PowerBuilder 10.5 was built previously before Window7 came out and the big also the obvious fact that this application was built within a Windows XP 32-bit environment. The 32-bit PowerBuilder application spits out the following error message when deployed on a Windows 7 64-bit machine. Application Terminated. Error: Invalid DataWindow row/column specified at line 44 in function ivvisiblecolumn of object objectwindow The database profile setup points

I am interested to check out whether column has an autoincrement/allowdbnull property . Having this code below , gives me always false although I already have one column that has autoincrement/allowdbnull property. Dim dt As New DataTable() Dim con As String = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source =" & Application.StartupPath & "\test.mdb" Dim sql As String = "SELECT * from teachers" Dim i As Integer Dim dataAdapter As New OleDb.OleDbDataAdapter(sql, con) dataAdapter.Fill(dt) dataAdapter.Dispose() For Each column As DataColumn In dt.Columns TextBox1.Text = TextBox1.Text & column

Althoug both Jet/OLE DB parameters are relativly well documented I fail to understand the difference between these two connection parameters: The first one: Jet OLEDB:Transaction Commit Mode (DBPROP_JETOLEDB_TXNCOMMITMODE) Indicates whether Jet writes data to disk synchronously or asynchronously when a transaction is committed. The second one: Jet OLEDB:User Commit Sync (DBPROP_JETOLEDB_USERCOMMITSYNC) Indicates whether changes that were made in transactions are written in synchronous or asynchronous mode. What's the difference? When to use which? This is very long, so here's the short answer:

I have several clients running an external executable using a C++ DLL to do bulk inserts though OLEDB into the same SQL Server table. The table has no indices, just a check constraint and a default. After I upgraded from SQL Server 2005 to 2008, all of a sudden I'm seeing deadlocks. The deadlock XDL (anonymized): <deadlock-list> <deadlock victim="process8057f048"> <process-list> <process id="process8057f048" taskpriority="0" logused="0" waitresource="OBJECT: 21:1176443315:0 " waittime="3329" ownerId="33387042" transactionname="SetCnstNotTrusted" lasttranstarted="2011-10-05T09:15:12.227" XDES=

I have created a software using VB.NET in a 32-bit Windows 7 OS. It contains those line of codes below: Dim cn As New OleDbConnection cn.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=" & fileNameStr & ";Jet OLEDB:Database Password=xxxxxxx" cn.Open() The codes open a MDB file (Microsoft Access file) protected by a password. When I run the software in my computer, it works well. However, when it is tested in another computer, an error message appears saying "Cannot open a database created with a previous version of your application." The error message is shown after the third