OLEDB TRANSACTION MAKING DIFFERENCE and error is raised

OLEDB transaction is making difference in my migrated application powerbuilder 10.5 which has new oledb driver which is replaced by MSS driver in previous Powerbuilder version.

1.)I am facing the below error on update/save this was not faced during my previous versino drive MSS in powerbuilder.This is oocure only after the change to oledb driver.

"Row change between retrieve and update.".

in front end of my application the error is poped as

"(STD1007) This row has been modified by another user. Save is canceled! ".

Please help to resolve this error.

Are you seeing this error when using Integration Services? If so, can you give more information on all the database access (e.g. ExecuteSQL, OLE DB Destination) in your package? If not, and this is specific to Powerbuilder, then I would start by looking at any settings available in your front end for handling database changes and transaction isolation level. If you want to focus on the provider itself, you can ask your question on the SQL Server Data Access forum, but they will likely have to rely on you to know how Powerbuilder is using the provider under the covers.

OLEDB Error when using Visual FoxPro Driver

Hi all,

I created a package that extracts records from a .DBF file into an SQL Server database. I installed a Visual FoxPro plugin (vfpoledb). When I run the package from my PC, it runs smoothly. But, when I try to run the same package in another PC, it displays a DTS_E_OLEDBERROR "Class not registered" error. Anyone has an idea about what this means? thanks in advance.
Is the OLE DB driver correctly installed in the other PC? If the package runs fine in one PC, then I doubt is a SSIS issue.|||Yes, the OLEDB is installed properly in the other PC. The driver is also installed in the Database Server. Still the problem occurs. I also tried placing and running the SSIS package in the database server but the same problem is encountered. I'm running out of ideas as to what might have caused the problem. What might be the cause(s) of the problem?

Thanks.
|||

Could you try using this provider with some other client?

Thanks,

Bob

OLEDB Error when using Visual FoxPro Driver

Hi all,

I created a package that extracts records from a .DBF file into an SQL Server database. I installed a Visual FoxPro plugin (vfpoledb). When I run the package from my PC, it runs smoothly. But, when I try to run the same package in another PC, it displays a DTS_E_OLEDBERROR "Class not registered" error. Anyone has an idea about what this means? thanks in advance.
Is the OLE DB driver correctly installed in the other PC? If the package runs fine in one PC, then I doubt is a SSIS issue.|||Yes, the OLEDB is installed properly in the other PC. The driver is also installed in the Database Server. Still the problem occurs. I also tried placing and running the SSIS package in the database server but the same problem is encountered. I'm running out of ideas as to what might have caused the problem. What might be the cause(s) of the problem?

Thanks.
|||

Could you try using this provider with some other client?

Thanks,

Bob

OLEDB driver omits SP return value

Hi,

I have a problem with some ATL7/OLEDB code. I'm trying to execute stored procedures from my application. I do get a result set back, but I never get a correct return value back. I've been going through MSDN articles as well as other articles on the web, and I just cannot see what I'm doing wrong!

I have this piece of ATL code:
<pre>
// code generated on den 6 juni 2002, 10:56

[
db_command(L"{ ? = CALL dbo.MyProc(?) }")
]
class CMyProc
{
public:
[ db_column(1, status=m_dwIdStatus, length=m_dwIdLength) ] LONG m_Id;
/* and so on - 7 columns total */

[ db_param(1, DBPARAMIO_OUTPUT) ] LONG m_RETURN_VALUE;
[ db_param(2, DBPARAMIO_INPUT) ] LONG m_id;

void GetRowsetProperties(CDBPropSet* pPropSet)
{
pPropSet->AddProperty(DBPROP_CANFETCHBACKWARDS, true, DBPROPOPTIONS_OPTIONAL);
pPropSet->AddProperty(DBPROP_CANSCROLLBACKWARDS, true, DBPROPOPTIONS_OPTIONAL);
}
};

</pre>

When I use this code I do:
<pre>
CSession dbsession;
CDataSource dbsource;
CDBPropSet dbinit(DBPROPSET_DBINIT);
/* fill dbinit with connection parameters */
/* HRESULTs not checked for brevity*/
dbsource.Open(_T("SQLOLEDB.1"), &dbinit);
dbsession.Open(dbsource);

CMyProc proc;
proc.m_id = 1;
proc.Open(dbsession);

TRACE("Return value is %d\n", proc.m_RETURN_VALUE);

/* Take care of result set - which exists and is valid! */
</pre>

The return value is <tt>-858993460</tt> which is <tt>0xcccccccc</tt>. In Visual C++ this value is used as an "uninitialized" stack value during debug. It seems as if ATL never bothers to update my return value parameters! I even made a little experiment with an extra output parameter - same thing there.

I'm using Visual C++ .NET and the SQL 2000 OLEDB provider (SP2). I've also tried this without attributed programming in both Visual C++ .NET and Visual C++ 6.

Does anybody have a clue what is going on??Is the stored procedure using set nocount on ? If not, put it in the stored procedure.

Good luck.|||Thanks for replying!

I tried with and without nocount and had no success.

I tried something else the other day though; I generated a non-attributed CCommand-class using CMultipleResults as template parameter. Then I could get all out parameters by calling GetNextResult() on the command object.

So my question is now; how do I make the attribute-injector generate a CCommand class for me using CMultipleResults?

OLE DB2 driver for Reporting Services

Question: When will the OLEDB driver be available for Reporting Services? In the Marketing Material I noted that Reporting Services can indeed connect to AS/400 through OLEDB. I have tried with all supplied OLEDB drivers and get only errors. The only drivers which work are ODBC and they are dog-slow. I have reviewed most posts on OLEDB drivers for AS/400 or DB2 and most everything points to SSIS. I want to be able to connect to the AS/400 through Reporting Services (SSRS) and report off it via an OLEDB driver instead of ODBC as I am doing it right now. Are there ANY implementable alternatives out there anybody?According to the SQL Server Feature Pack, the Microsoft OLEDB for DB2 driver can be used with Reporting Services.

http://www.microsoft.com/downloads/details.aspx?familyid=50b97994-8453-4998-8226-fa42ec403d17&displaylang=en

OLE DB drivers and Vista 64 bit

I am trying to load a Fox Pro file which I used to be able to load before I installed 64 bit Vista. I'm using ver 9 of the fox pro driver. I don't know if it's a driver problem or something else I am doing wrong.

Here's the error msg:

SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154.

An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".

Error: 0xC020801C at Load Country, OLE DB Source [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "C:\Users\john.church.LLC\Desktop\MaxMin\AccountingSystem Database\AccountingSystem Database\AccountingSystem.DBC" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.

But then it also says something about registering a class. I'm a .net moron so I'm not sure what that means.

Any thoughts?

Thanks.

(Vista 64, SQL Svr 2005 64, visual studio - with all known updates/patches installed)

Hi John,The VFP OLE DB data provider isn't 64-bit compatible.|||"Does Microsoft have a 64 bit driver?" he asked, laughing and shaking his head.|||Not for Visual FoxPro, and there are no plans to create one.|||Kinda what I figured. Now my only decision is whether to go back to Vista 32 or XP.........has MS announced when they're going to cancel Vista yet?

Old SQL ODBC driver on 2003 Server

Anyone run into this.
I have a Windows 2003 Server which has a very old sql Server ODBC Driver
installed. If I go into Data Sources and view the SQL Server driver it is
dated back in 1997. Very old and I suspect that when someone installed 6.5
SQL Server tools, it overwrote the newer driver.
Bottom line, how do I re-install SQL Server Driver, or other ODBC drivers
for that matter on a 2003 server without reinstalling the OS?
Eric Correa
Windows Server Engineer
Try installing the latest MDAC (version 2.8, I think). You can get that from the Microsoft site.
"Eric Correa" <EricCorrea@.discussions.microsoft.com> wrote in message
news:7ADBEB08-8E19-4B1A-B25D-95CFEA94C915@.microsoft.com...
> Anyone run into this.
> I have a Windows 2003 Server which has a very old sql Server ODBC Driver
> installed. If I go into Data Sources and view the SQL Server driver it is
> dated back in 1997. Very old and I suspect that when someone installed 6.5
> SQL Server tools, it overwrote the newer driver.
> Bottom line, how do I re-install SQL Server Driver, or other ODBC drivers
> for that matter on a 2003 server without reinstalling the OS?
> --
> Eric Correa
> Windows Server Engineer
|||You cannot install MDAC 2.8 on a Windows 2003 Server. Not allowed.
Eric Correa
Windows Server Engineer
"Scot T Brennecke" wrote:

> Try installing the latest MDAC (version 2.8, I think). You can get that from the Microsoft site.
> "Eric Correa" <EricCorrea@.discussions.microsoft.com> wrote in message
> news:7ADBEB08-8E19-4B1A-B25D-95CFEA94C915@.microsoft.com...
>
>
|||You will need to run an "update install" of Windows 2003 (or you could
re-install Windows 2003 SP1).
An "update install" is you just pop in the Windows 2003 CD and say you are
going to install it. The setup will prompt you if you want to do an "update
install" say yes. This is sort of like a repair install so to speak.
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Eric Correa" <EricCorrea@.discussions.microsoft.com> wrote in message
news:745D9A13-B613-41A0-A949-63D9B712597F@.microsoft.com...[vbcol=seagreen]
> You cannot install MDAC 2.8 on a Windows 2003 Server. Not allowed.
> --
> Eric Correa
> Windows Server Engineer
>
> "Scot T Brennecke" wrote:

Old SQL ODBC driver on 2003 Server

Anyone run into this.
I have a Windows 2003 Server which has a very old sql Server ODBC Driver
installed. If I go into Data Sources and view the SQL Server driver it is
dated back in 1997. Very old and I suspect that when someone installed 6.5
SQL Server tools, it overwrote the newer driver.
Bottom line, how do I re-install SQL Server Driver, or other ODBC drivers
for that matter on a 2003 server without reinstalling the OS?
Eric Correa
Windows Server EngineerTry installing the latest MDAC (version 2.8, I think). You can get that fro
m the Microsoft site.
"Eric Correa" <EricCorrea@.discussions.microsoft.com> wrote in message
news:7ADBEB08-8E19-4B1A-B25D-95CFEA94C915@.microsoft.com...
> Anyone run into this.
> I have a Windows 2003 Server which has a very old sql Server ODBC Driver
> installed. If I go into Data Sources and view the SQL Server driver it is
> dated back in 1997. Very old and I suspect that when someone installed 6.5
> SQL Server tools, it overwrote the newer driver.
> Bottom line, how do I re-install SQL Server Driver, or other ODBC drivers
> for that matter on a 2003 server without reinstalling the OS?
> --
> Eric Correa
> Windows Server Engineer|||You cannot install MDAC 2.8 on a Windows 2003 Server. Not allowed.
--
Eric Correa
Windows Server Engineer
"Scot T Brennecke" wrote:

> Try installing the latest MDAC (version 2.8, I think). You can get that f
rom the Microsoft site.
> "Eric Correa" <EricCorrea@.discussions.microsoft.com> wrote in message
> news:7ADBEB08-8E19-4B1A-B25D-95CFEA94C915@.microsoft.com...
>
>|||You will need to run an "update install" of Windows 2003 (or you could
re-install Windows 2003 SP1).
An "update install" is you just pop in the Windows 2003 CD and say you are
going to install it. The setup will prompt you if you want to do an "update
install" say yes. This is sort of like a repair install so to speak.
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Eric Correa" <EricCorrea@.discussions.microsoft.com> wrote in message
news:745D9A13-B613-41A0-A949-63D9B712597F@.microsoft.com...[vbcol=seagreen]
> You cannot install MDAC 2.8 on a Windows 2003 Server. Not allowed.
> --
> Eric Correa
> Windows Server Engineer
>
> "Scot T Brennecke" wrote:
>