odbc drivers for btrieve for sql

Does anyone know where I can find odbc drivers so I can cannect to a btrieve
database from sql 2000? Are there native sql 2000 drivers that support
this?
Thanks,
Jim'BTrieve' is now 'Pervasive'
http://www.pervasive.com/integratio...odbcvendors.asp
"Jims" <biz@.neocasa.net> wrote in message
news:#KtFZX4XEHA.3420@.TK2MSFTNGP12.phx.gbl...
> Does anyone know where I can find odbc drivers so I can cannect to a
btrieve
> database from sql 2000? Are there native sql 2000 drivers that support
> this?
> Thanks,
> Jim
>

odbc drivers for btrieve for sql

Does anyone know where I can find odbc drivers so I can cannect to a btrieve
database from sql 2000? Are there native sql 2000 drivers that support
this?
Thanks,
Jim
'BTrieve' is now 'Pervasive'
http://www.pervasive.com/integration...dbcvendors.asp
"Jims" <biz@.neocasa.net> wrote in message
news:#KtFZX4XEHA.3420@.TK2MSFTNGP12.phx.gbl...
> Does anyone know where I can find odbc drivers so I can cannect to a
btrieve
> database from sql 2000? Are there native sql 2000 drivers that support
> this?
> Thanks,
> Jim
>

odbc drivers for btrieve for sql

Does anyone know where I can find odbc drivers so I can cannect to a btrieve
database from sql 2000? Are there native sql 2000 drivers that support
this?
Thanks,
Jim'BTrieve' is now 'Pervasive'
http://www.pervasive.com/integration/support/odbcvendors.asp
"Jims" <biz@.neocasa.net> wrote in message
news:#KtFZX4XEHA.3420@.TK2MSFTNGP12.phx.gbl...
> Does anyone know where I can find odbc drivers so I can cannect to a
btrieve
> database from sql 2000? Are there native sql 2000 drivers that support
> this?
> Thanks,
> Jim
>

ODBC Driver for SQLServer Everywhere/Compact from Access

So far I've been unable to connect to a test SQLServer Everywhere/Compact database with MS Access. I installed the new SQLServer 2005 Native Client to no avail. Has anyone done this?

If you are trying to sync the data between Access and the SQLServer Compact edition, you might need to download the synchronizer. The following link should provide you a quick overview and the access to the software. If this is not what you intended to do, please provide more details on what you are trying to accomplish:

http://www.microsoft.com/downloads/details.aspx?FamilyID=B967347A-5DD0-445C-8A9F-AEA3DB9EC4BC&displaylang=en

Regards,

Riyaz

|||

In Access, I'm simply trying to link to a SQLServer CE database using an ODBC driver, as you can do with other SQLServer servers. I've been the route you suggested, hoping that in the process I'd discover the driver I need. But to install that synchronizer, I have to install IIS and SQLServer 2005, which goes beyond what I'm trying to do. And I'm not interested in syncronizing to a mobile device in any case.

I was hoping to use SQLServer CE as a substitute for the normal Access Jet engine, to take advantage of encryption and security that Access does not provide (or does poorly). I want to deploy a single-user Access application with an easily deployable secure database. I'm doing it now with just Access, but I'd like to make the data tables inaccessible except through my application.

Thanks for the suggestion.

|||You can only connect to an instance of a SQL Server 2005 Mobile Edition database when it is running on a Windows CE-based OS or Tablet PC (you can create a SQL Server 2005 Mobile database in Visual Studio and, I believe, SQL Server Management Studio as part of the development process). When SQL Server Everywhere becomes available, it should, as you've surmised, fit your needs. In the meantime, you can check out the development experience using SQL Mobile today...take a look at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/sqleverywhere.asp?frame=true for some additional info. If you'd like to have a runtime prototype of your app, however, you'll want to try using SQL Server 2005 Express.|||

I do have SQL Server 2005 Everywhere installed, (SQL Server 2005 Compact Edition), and I've created a database from VS 2005 (after installing VS 2005 SP1 Beta) and so far have not been able to connect to that database from Access. There is a .dll distributed with Everywhere: sqlceoledb30.dll that has a description "OLEDB Provider" that I am hoping will work, but it is not installed as an ODBC driver.

It seems impossible that I'm the first to attempt this. Any help will be appreciated.

Office 2003 SP2, Win XP SP2, VS 2005 SP1 Beta

Thanks

|||

The naming is a little tricky here...SQL Server 2005 Mobile Edition is the 3.0 version of the product formerly referred to as SQL Server Compact Edition (or SQL CE). The product formerly referred to as SQL Server Everywhere now appears to have the moniker of SQL Server 2005 Compact Edition...this version is the only one in this family that can be used on the desktop. A CTP version of this product was released in late August and the RC1 version is now available at http://www.microsoft.com/downloads/details.aspx?FamilyId=85E0C3CE-3FA1-453A-8CE9-AF6CA20946C3&displaylang=en

Given all of this, which version do you have? The RC1 file version appears to be 3.1 (the device only SQL Server 2005 Mobile Edition would be v3.0, I believe).

If you have the correct version but continue to have problems connecting, I'll move this thread into the SQL Server Compact Edition forum.

|||

If you read the last post I made, it's pretty clear that I have Compact Edition 3.1 RC1 Beta. I haven't ever installed the Mobile Edition. After installing CE, most references (like the installation directory) reflect the previous name (Everywhere).

I really want to link to a Compact Edition database through ODBC (as it happens, in Access). I can connect to it fine in VS 2005 VB.NET, so I don't think it's a lack of understanding.

Thanks, any help will be appreciated.

|||Thanks for claryifying the specific version that you have installed. Someone here in the SQL Server Compact Edition forum should be able to help you with the nuances of connecting to a local SQL Server CE database.|||

Although SQL CE 3.1 does expose an OLE DB provider, you cannot link to it via the regular ODBC link in Access. I have developed a set of tools that will help you with both converting to and from Access and also to edit the SDF on the desktop. These tools use the OLE DB provider at the low level and work with databases on the PC and on the device. You can try them here: http://www.primeworks-mobile.com

ODBC Call Fail/Record locked

I have recently moved some native Access tables to SQL Server 7. These tables are updated in code. When the update is done via a SQL statement, I get
"This record is being modified by another user. . . Save, Copy to Clipboard, Drop Changes"

When the record is being updated via DAO code, I get,
"ODBC Call Fail"

Both errors are most irritating and I desperately need to find a way around this. Any suggestions would be greatly appreciated.

CrystalHi there,

Maybe this information helps you on the way...

-- Microsoft Knowledge Base Article - 128809

-- Zoek in de Google nieuwsgroepen naar Onderwerp:
"auto_increment fields and #Deleted in MS Access?"
Nieuwsgroep:
-> mailing.database.myodbc

Greetz,
DePrins
:)

ODBC call fail/ Record Locked

I am in the process of moving native Access tables over to
SQL Server 7. These tables are updated through code.
Some are updated with SQL statements executed through a db
object and others are updated using DAO.
When I update using SQL, I get "This record is being
modified by another user. . . Save, Copy to Clipboard,
Drop Changes."
When I update using DAO, the code crashes on the .Update
command and says, "ODBC call fail."
I can update the tables manually without error.
Is there a way to fix this? What am I doing wrong in the
code?
Crystal
You should seriously consider getting rid of all DAO code that
performs DML against SQL Server tables. It's the slowest, buggiest,
and least-efficient way of performing any task. The reason is that you
are invoking an instance of the Jet engine on every call. The result
is that the call goes through Jet-ODBC-SQL Server. However, if you use
SQL statements in a pass-through query, the statement is passed
directly to SQL Server, where it is executed on the server. This
results in faster, more efficient transactions. Pass-through queries
also give you the capability of calling stored procedures, and can be
used as the basis of reports. If you must use recordsets for some
reason, use ADO, not DAO when going against SQL Server data.
-- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446
On Mon, 3 May 2004 06:32:13 -0700, "Crystal"
<anonymous@.discussions.microsoft.com> wrote:

>I am in the process of moving native Access tables over to
>SQL Server 7. These tables are updated through code.
>Some are updated with SQL statements executed through a db
>object and others are updated using DAO.
>When I update using SQL, I get "This record is being
>modified by another user. . . Save, Copy to Clipboard,
>Drop Changes."
>When I update using DAO, the code crashes on the .Update
>command and says, "ODBC call fail."
>I can update the tables manually without error.
>Is there a way to fix this? What am I doing wrong in the
>code?
>Crystal

ODBC call fail/ Record Locked

I am in the process of moving native Access tables over to
SQL Server 7. These tables are updated through code.
Some are updated with SQL statements executed through a db
object and others are updated using DAO.
When I update using SQL, I get "This record is being
modified by another user. . . Save, Copy to Clipboard,
Drop Changes."
When I update using DAO, the code crashes on the .Update
command and says, "ODBC call fail."
I can update the tables manually without error.
Is there a way to fix this? What am I doing wrong in the
code?
CrystalYou should seriously consider getting rid of all DAO code that
performs DML against SQL Server tables. It's the slowest, buggiest,
and least-efficient way of performing any task. The reason is that you
are invoking an instance of the Jet engine on every call. The result
is that the call goes through Jet-ODBC-SQL Server. However, if you use
SQL statements in a pass-through query, the statement is passed
directly to SQL Server, where it is executed on the server. This
results in faster, more efficient transactions. Pass-through queries
also give you the capability of calling stored procedures, and can be
used as the basis of reports. If you must use recordsets for some
reason, use ADO, not DAO when going against SQL Server data.
-- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446
On Mon, 3 May 2004 06:32:13 -0700, "Crystal"
<anonymous@.discussions.microsoft.com> wrote:

>I am in the process of moving native Access tables over to
>SQL Server 7. These tables are updated through code.
>Some are updated with SQL statements executed through a db
>object and others are updated using DAO.
>When I update using SQL, I get "This record is being
>modified by another user. . . Save, Copy to Clipboard,
>Drop Changes."
>When I update using DAO, the code crashes on the .Update
>command and says, "ODBC call fail."
>I can update the tables manually without error.
>Is there a way to fix this? What am I doing wrong in the
>code?
>Crystal

ODBC Access Link to SS2K5-Cannot update new records.

Access 2003 connected via ODBC using
ODBC;Driver={SQL Native
Client};Server=ServerName;Database=DbNam
e;UID=xx;PWD=xxx
Originally the data was imported from Access tables. All imported records
can be edited or updated without a problem but new records created from
access using code or access table views cannot be edited.
The returned error:
The records has been changed by another since you started editing it. ...
If a record is copied from an existing record by cutting and pasting the
complete record in an access table view then it is ok but if the record is
added by going to the new record (*) at the bottom of the table and adding
the one field that does not allow nulls then the autonumber gets updated
properly but none of the other fields can be edited.
It appears the SS2K5 server will not allow the access application to delete
one of the records that cannot be edited either.
The error:
The Microsoft Jet dtabase engine stopped the process because you and another
user are attempting to change the same data at the same time.
If you log into the Server using Management Studio with the same credentials
you can do anything you want.
Looked a differnet connection strings but am not aware of an ODBC
configuration with record locking directives.
Thanks in advance for any help you might offer.
RobGMillerIt's hard to diagnose a problem like this without being able to see
the database schema and the application/form code. One thing that
often helps is to add a timestamp column to the table. This lets
Access know if a row has been altered by another process since it was
fetched.
-Mary
On Fri, 14 Dec 2007 12:43:02 -0800, RobGMiller
<RobGMiller@.discussions.microsoft.com> wrote:

>Access 2003 connected via ODBC using
>ODBC;Driver={SQL Native
> Client};Server=ServerName;Database=DbNam
e;UID=xx;PWD=xxx
>Originally the data was imported from Access tables. All imported records
>can be edited or updated without a problem but new records created from
>access using code or access table views cannot be edited.
>The returned error:
>The records has been changed by another since you started editing it. ...
>If a record is copied from an existing record by cutting and pasting the
>complete record in an access table view then it is ok but if the record is
>added by going to the new record (*) at the bottom of the table and adding
>the one field that does not allow nulls then the autonumber gets updated
>properly but none of the other fields can be edited.
>It appears the SS2K5 server will not allow the access application to delete
>one of the records that cannot be edited either.
>The error:
>The Microsoft Jet dtabase engine stopped the process because you and anothe
r
>user are attempting to change the same data at the same time.
>If you log into the Server using Management Studio with the same credential
s
>you can do anything you want.
>Looked a differnet connection strings but am not aware of an ODBC
>configuration with record locking directives.
>Thanks in advance for any help you might offer.