Home : OPSSQL RSVIEW32 and error 3265
Q10456 - SUPPORT: OPSSQL RSVIEW32 and error 3265

If you get the error 3265 or the message about could not connect or wrong format, then there are a few points to check. Open the INTERFACE.INI file in Notepad.

1. First check the connection strings in the INI file. They look something like:

DBTYPE=2
1=Provider=OraOLEDB.Oracle.1;Data Source=ORADEV;User ID=@@@;Password=###;
2=Provider=SQLOLEDB;Data Source=LT035\OPSSQL;initial catalog=@@@;User Id=OPSDBA;Password=###;OLE DB Services =-2;

Make sure the Data Source for either connection is correct. Line '1=' is the Oracle connection and line '2=' is the MS SQL.

2. Next, check the source connection string. For RSVIEW32, Data Source points to a folder of dBase IV files. If you bring up windows explorer and navigate to that folder, you should see files with the extension .DBF.

USERCON1=Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\OPSSQL\OPSSQL_RSVIEW32\Auburn;Extended Properties=dBASE IV;User ID=Admin;Password=;

3. One other item to check in the INTERFACE.INI is the DATABASE line as shown below:

DATABASE=OPSAUBURN~1

This line looks fine and will work as long as OPSAUBURN exists. In older versions of RSVIEW32, however, the program had put and extra '~0' on the end - like this 'DATABASE=OPSAUBURN~1~0' - This was designed for an offset, but when set to 0, it causes the error 3265 when running the RSVIEW32 interface.

 


 

Related Articles
No Related Articles Available.

Article Attachments
No Attachments Available.

Related External Links
No Related Links Available.
Help us improve this article...
What did you think of this article?

poor 
1
2
3
4
5
6
7
8
9
10

 excellent
Tell us why you rated the content this way. (optional)
 
Approved Comments...
No user comments available for this article.
Created on 9/20/2007 10:49 AM.
Last Modified on 9/20/2007 10:49 AM.
Last Modified by No Author Name Available!.
Suggested by Les Poyner
Article has been viewed 3859 times.
Rated 9 out of 10 based on 2 votes.
Print Article
Email Article