OLEDB Connection String

[chel123]

Hi All,

I've just joined today and hoping you'll be able to help me with MS Access issues. I haven't used MS Access for quite some time, nor even expert on this field. We have some small applications built from it, which our users are only using it once in a while.

Currently I'm struggling on how I can import from our universe database using MS Access 2003. We're doing this at least once a year and somehow when running the same report this year, we are getting this error: (3021, Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.)

To verify on this, I've tried running the same report from our application server (running in unix) and I've got results. But when trying to connect from MS Access, it seems the recordset is always empty.

I'm using IBM UniVerse ODBC Driver 4.00.03.7251 and my OLEDB Connection string is as follows:

Provider=MSDASQL.1;Persist Security Info=False;Extended Properties="DSN=Edmptis;DB=Edmptis;PWD=ptis;UID=edminq;LMX=4096;PSZ=10;PTH=5;SDT=No;SAT=No;SFS=No;SSN=No;SNQ=No;SCT=No;SNT=No;UVN=Yes;RTY=No;Use FileInfo=No;RXP=512;AIR=1"

Where 'edmptis' is our application server. The given userid and password are correct and working fine when logging from the server.

Can you please confirm if there has been changes recently on how we configure from OLEDB Connection String in this kind of situation?

If so, can you please let me know?

Would appreciate your help on this.

Thanks & Regards,
Chel

 

[Galaxiom]

You are using ODBC so you will want an ODBC connection string.

Unfortunately Universe experience is not very common at this site.

If I had a copy of the ODBC driver I would try it on our system. Unfortunately it wasn't provided with our system and I missed the chance to get it before IBM sold their business and the new owners took down the free trial version which included it.

 

[chel123]

Finally I was able to fix this problem. The reason why my UniVerse ODBC driver can't establish connection to the universe database residing in our server, is because the uci config file which used to access UniVerse data is still pointing to the hostname that has old ip address, which we're not using anymore. I've changed the hostname into the new server that we're currently using and everything worked fine. I was able to connect to the database and run the import. Thanks to the one who replied on this.