BDE Migration to UniDAC with Sybase
BDE Migration to UniDAC with Sybase
Hi Everyone
We are planing to migrate from BDE to UniDAC on Delphi 10 with Sybase 15.
Could you please let us know is there any limitations with UniDAC and Sybase combination?
Thanks in advance!!
SP
We are planing to migrate from BDE to UniDAC on Delphi 10 with Sybase 15.
Could you please let us know is there any limitations with UniDAC and Sybase combination?
Thanks in advance!!
SP
Thanks alex..do we have any documents for setting up connections and usage of components?AlexP wrote:Hello,
UniDAC works with Sybase through ODBC driver, so UniDAC supports the same functionality implemented by specific ODBC driver.
we tried connection with harcoded values..as am new to ODBC settings am stuggling to find the way..
Hello,
You can connect to the server like:
var
UniConnection: TUniConnection;
begin
UniConnection:= TUniConnection.Create(nil);
UniConnection.ProviderName := 'ASE';
UniConnection.Server := '.....';//server name
UniConnection.Port := 5000; //port
UniConnection.Username := '..'; //login
UniConnection.Password := '...';//password
try
UniConnection.Connect;
ShowMessage(UniConnection.ServerVersion);
finally
UniConnection.Free;
end;
You can find more information about setting up connections and using components in the UniDAC help.
You can connect to the server like:
var
UniConnection: TUniConnection;
begin
UniConnection:= TUniConnection.Create(nil);
UniConnection.ProviderName := 'ASE';
UniConnection.Server := '.....';//server name
UniConnection.Port := 5000; //port
UniConnection.Username := '..'; //login
UniConnection.Password := '...';//password
try
UniConnection.Connect;
ShowMessage(UniConnection.ServerVersion);
finally
UniConnection.Free;
end;
You can find more information about setting up connections and using components in the UniDAC help.
Hi
Thanks its working, but when I set the provider name as ASE, still its trying to connect to the database using ODBC Driver.
Also, it expects the hostname rather than the alias server as mentioned in sql.ini file in the Parameter value for the Server.
The value passed is @@servername to the server.
I am getting the below error message
Exception Raised [Sybase][ODBC Driver] Client unable to establish the connection
Thanks in advance
Thanks its working, but when I set the provider name as ASE, still its trying to connect to the database using ODBC Driver.
Also, it expects the hostname rather than the alias server as mentioned in sql.ini file in the Parameter value for the Server.
The value passed is @@servername to the server.
I am getting the below error message
Exception Raised [Sybase][ODBC Driver] Client unable to establish the connection
Thanks in advance
Hello,
In both cases (using the ASE and ODBC providers) UniDAC connects to Sybase via the ODBC driver. The difference between the ASE and ODBC providers is that with ODBC you should create DSN and use it as a server name, and with ASE you can connect using only hostname.
Unfortunately, now UniDAC does not support working with Sybase ASE using sql.ini.
We will investigate the possibility of adding this feature in one of the next versions.
In both cases (using the ASE and ODBC providers) UniDAC connects to Sybase via the ODBC driver. The difference between the ASE and ODBC providers is that with ODBC you should create DSN and use it as a server name, and with ASE you can connect using only hostname.
Unfortunately, now UniDAC does not support working with Sybase ASE using sql.ini.
We will investigate the possibility of adding this feature in one of the next versions.
Hi
Thanks for the information.
But any idea when this issue will be fixed as after migration we are planning to rollout in Production on all user machines where we have sql.ini file in place.
Also, The UniStoredProc component is retreiving the param names from database at design time without @
Eg : It will define the name as attr1 instead of @attr1 . In BDE, it was fetching the params like @attr1
Any idea why there is a difference or we have any option for param name check in TuniStoredProc
Regards
SP
Thanks for the information.
But any idea when this issue will be fixed as after migration we are planning to rollout in Production on all user machines where we have sql.ini file in place.
Also, The UniStoredProc component is retreiving the param names from database at design time without @
Eg : It will define the name as attr1 instead of @attr1 . In BDE, it was fetching the params like @attr1
Any idea why there is a difference or we have any option for param name check in TuniStoredProc
Regards
SP
Thanks a lot ..Appreciate your support,it would be greatful to us if the build comes in next 2weeksAlexP wrote:Hello,
We will try to add support of sql.ini as soon as posible.
We will investigate the possibility of adding '@' to to names of procedure parameters, but that is hardly to happen in the nearest future.
Now you need to change parameters names manually
Hi
When defining the storedproc the parameters are getting populating from backend stored procedure but param type(in/out) is not getting..could you please let me know is there any settings to get those types...sorry to bug you more..i wasted my most of the time with dbexpress/sybase..which ended me with somany issues
now am using unidac as of now i didnt see any major show stoppers..only thing i hv got above 2issues now this is the 3rd one which may take much of time..becuase manually i can easily change code but for this i need to click on the object and and i need to change each and every param type..please help me..i remember when i tested unidac 1st time i got the param type also now am not getting.
Thanks in advance!!
SP
When defining the storedproc the parameters are getting populating from backend stored procedure but param type(in/out) is not getting..could you please let me know is there any settings to get those types...sorry to bug you more..i wasted my most of the time with dbexpress/sybase..which ended me with somany issues
Thanks in advance!!
SP
EODBCError with message"[MERANT][ODBC Sybase ASE driver]String data,right truncated.Error in parameter 23.
Scenario 1
----------
select dlast from tlastdate--> Jan 1 2099 12:00AM
I am getting as datetime and passing to storedproc as datetime still am getting this error..
ParamByName('insert23').AsDateTime := FixedDate;
Scenario 2
----------
ParamByName('insert23').AsDateTime := '1/1/2099'
Same error as above
Scenario 3
----------
ParamByName('insert23').AsDateTime := StrtoDateTime('1/1/2099')
Same error as above
Scenario 4
------------
ParamByName('insert23').AsDateTime := StrtoDateTime('Jan 1 2099 12:00AM')
Invalid date format
Please help me..
Scenario 1
----------
select dlast from tlastdate--> Jan 1 2099 12:00AM
I am getting as datetime and passing to storedproc as datetime still am getting this error..
ParamByName('insert23').AsDateTime := FixedDate;
Scenario 2
----------
ParamByName('insert23').AsDateTime := '1/1/2099'
Same error as above
Scenario 3
----------
ParamByName('insert23').AsDateTime := StrtoDateTime('1/1/2099')
Same error as above
Scenario 4
------------
ParamByName('insert23').AsDateTime := StrtoDateTime('Jan 1 2099 12:00AM')
Invalid date format
Please help me..
ignore this..i did formatdatetime('mm/dd/yyyy',FixedDate) ...sasdua wrote:EODBCError with message"[MERANT][ODBC Sybase ASE driver]String data,right truncated.Error in parameter 23.
Scenario 1
----------
select dlast from tlastdate--> Jan 1 2099 12:00AM
I am getting as datetime and passing to storedproc as datetime still am getting this error..
ParamByName('insert23').AsDateTime := FixedDate;
Scenario 2
----------
ParamByName('insert23').AsDateTime := '1/1/2099'
Same error as above
Scenario 3
----------
ParamByName('insert23').AsDateTime := StrtoDateTime('1/1/2099')
Same error as above
Scenario 4
------------
ParamByName('insert23').AsDateTime := StrtoDateTime('Jan 1 2099 12:00AM')
Invalid date format
Please help me..
thanks alex..let me try...AlexP wrote:Hello,
The ParamType properties are correctly detected by default, you shouldn't set any options to get the ParamType properties.
Please try to reinstall UniDAC, maybe it'll help you to resolve this problem.
One more important Question..Do we need to have UniDAC Installed in Client machines to execute Delphi Exe or do we need distrubute to any DLL with the build...