- ProIV Resource Centre
- → Viewing Profile: Posts: Ralph Gadsby
Community Stats
- Group Members
- Active Posts 154
- Profile Views 7,045
- Member Title Expert
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Male
-
Location
United Kingdom
Previous Fields
-
First Name
Ralph
-
Surname
Gadsby
-
Nationality
English
-
Year Started ProIV
1989
-
Highest ProIV Version Used
5.5
-
Company Working For
Pro-IV Ltd.
-
Companies Worked For
MDIS,
Self,
Proinsure System Ltd
0
Neutral
User Tools
Friends
Ralph Gadsby hasn't added any friends yet.
Latest Visitors
Posts I've Made
In Topic: C-ISAM to RDBMS
08 August 2012 - 03:19 PM
Transoft U/SQL was always the way to go. I've never seen the CONNX driver, so can't comment on that.
In Topic: ProISAM error on Win2K Server
22 July 2003 - 01:34 PM
It would seem that there was a problem that the pisamevt.dll failed to register successfully in previous releases under certain circumstances. This problem was fixed in 5.5r200.
Fred, if you would like to log this fault with PROIV support we will investigate the cause of your problem.
Fred, if you would like to log this fault with PROIV support we will investigate the cause of your problem.
In Topic: New SQL Layer?!
22 July 2003 - 10:52 AM
Anyone running 5.5r208 or above will be using the new SQL layer. There are also a couple of customers with earlier kernels that have the new SQL layer patched in. The easiest way to determine whether you are running the new SQL layer is to enable tracing using TRACESQL=1 and then connect to a database. If you see lines in the trace file that begin with chevrons (< or >) then you have the new SQL layer. The SQL layer sits between the OCI/ODBC layer and the PROIV kernel. Consequently, the OCI layer has not been changed at all. However, we have made a number of improvements to the PROIV ODBC drivers, including adding support for a couple of new databases.
I will leave it to others to comment on the relative performance, as I have not performed any in depth quantitative benchmarking.
The SQL layer was rewritten primarily to address a number of issues that affected ODBC database connections. We also took the opportunity to improve the tracing within the SQL layer, so that any problems that may occur in the future will be able to be resolved more easily.
I will leave it to others to comment on the relative performance, as I have not performed any in depth quantitative benchmarking.
The SQL layer was rewritten primarily to address a number of issues that affected ODBC database connections. We also took the opportunity to improve the tracing within the SQL layer, so that any problems that may occur in the future will be able to be resolved more easily.
In Topic: Weird numeric conversion error?
21 July 2003 - 01:06 PM
Chris, I meant 'Numeric conversion error ' and 'Invalid character value for cast specification' messages. I guess that it is also possible that an invalid date error could be caused, however I am not aware of any one reporting this to us.
The new SQL layer went into the 5.5r208 production release.
The new SQL layer went into the 5.5r208 production release.
In Topic: ProISAM error on Win2K Server
21 July 2003 - 12:19 PM
Fred, you ought to have a pisamevt.dll in your WINNT\SYSTEM32 directory. From the fact that the event description is missing it would appear that you do not have this DLL (or the file is in the wrong location).
- ProIV Resource Centre
- → Viewing Profile: Posts: Ralph Gadsby
- Privacy Policy