BDE Migration to UniDAC with Sybase

sasdua · Post by **sasdua** » Mon 28 Mar 2011 14:36

AlexP wrote:Hello,

You do not need to deploy any files with UniDAC-based applications built without run-time packages, provided that you are using a registered version of UniDAC.
For more information, please see the Deployment topic in the UniDAC help.

Thanks a lot..

sasdua · Post by **sasdua** » Mon 28 Mar 2011 14:42

AlexP 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

Alex..when i use migration tool it is giving me param name with '@' but it is not getting me size of the parmater:(

AlexP · Post by **AlexP** » Tue 29 Mar 2011 10:09

Hello,

When you are using Migration Wizard, names of parameters are taken from a *.dfm file as is, so the '@' symbol is included into the parameter names.
UniDAC doesn't have the Size property for parameters, we will investigate the possibility of adding this feature in the next version of UniDAC.

sasdua · Post by **sasdua** » Wed 30 Mar 2011 13:36

Hi

Can you please let me know if there is any problem with unidac while comparing the blank or null values.

For the below query when I run in the backend , I am getting resultset but with Uniquery component not able to get any result set.
select l.*,s.tstate,c.tcountry,g.cgeo,g.tgeo
from tlocation l,tstate s,tcountry c,tgeo g
where l.clocation = 'LDN'
and l.cstate *= s.cstate
and l.ccountry *= c.ccountry
and (
(l.ccountry = g.ccountry and l.cstate = g.cstate)
or
(l.cstate = null and l.ccountry = g.ccountry)
)

We are facing similar problems with stored procs which gets the data from backend.

Thanks

AlexP · Post by **AlexP** » Thu 31 Mar 2011 08:17

Hello,

To compare fields with null values in UniDAC, you should use the following syntax:
.....
where T1.NullField is null
instead of
where T1.NullField = null

sasdua · Post by **sasdua** » Thu 31 Mar 2011 10:53

AlexP wrote:Hello,

To compare fields with null values in UniDAC, you should use the following syntax:
.....
where T1.NullField is null
instead of
where T1.NullField = null

thanks alex..one more added...now i hv to check all query components

sasdua · Post by **sasdua** » Fri 01 Apr 2011 10:57

AlexP wrote:Hello,

To compare fields with null values in UniDAC, you should use the following syntax:
.....
where T1.NullField is null
instead of
where T1.NullField = null

hello alex ..

got the issue..the issue is mainly becuase of precision UniProc is not getting precision and size value..

can you please fix the issue..atleast can you bring size of the parameter..when we migrate from BDE to Unidac

sasdua · Post by **sasdua** » Wed 06 Apr 2011 11:29

Hi,

Can you please let us know when comparisons are made for values and if one field has null value or blank will that get evaluated or will it not return the result set.

Eg : Save Proc
if col1 != @col2 and col2 has no value to compare, will this work?

We know that != null will not work and we need to replace this with is not null but could you please let us know for a general field comparison if the field does not have any value will that work or not as it is very important for us to migrate.

Regards,
Sas

AlexP · Post by **AlexP** » Thu 07 Apr 2011 08:45

Hello,

We have solved the problem.
To use the '=' or '!=' for comparison with null value you, should disable the ansinull options like:

procedure TForm1.UniConnection1AfterConnect(Sender: TObject);
begin
UniConnection1.ExecSQL('set ansinull off',[]);
end;

We will add this option to the specific >options for the ASE provider.

sasdua · Post by **sasdua** » Thu 07 Apr 2011 10:55

Thanks a lotttttttttttttttttt

sasdua · Post by **sasdua** » Thu 07 Apr 2011 11:12

AlexP wrote:Hello,

We have solved the problem.
To use the '=' or '!=' for comparison with null value you, should disable the ansinull options like:

procedure TForm1.UniConnection1AfterConnect(Sender: TObject);
begin
UniConnection1.ExecSQL('set ansinull off',[]);
end;

We will add this option to the specific >options for the ASE provider.

its working alex..cheers buddy..thanks a lot..really when i got the issue..i not thought of set options..

earlier i got issue with quotedstring when i tried using dbexpress..even we resloved tht issue with set options..

sasdua · Post by **sasdua** » Thu 07 Apr 2011 11:21

Please find the solution for sql.ini lookup also..which will help us a lot

AlexP · Post by **AlexP** » Fri 08 Apr 2011 08:54

Hello,

We have added the AnsiNull option, it will be available in the next build.
But unfortunately we have no time to include the Parameter size and SQL.Ini features to it. We plan to add these features in the next but one build.

sasdua · Post by **sasdua** » Mon 18 Apr 2011 15:40

Thanks a lot!!

sasdua · Post by **sasdua** » Wed 20 Apr 2011 12:53

Hi

Can you please let us know when you will be including the sql.ini feature.

We are finding it very difficult to integrate the build as we are passing the Server Name and not the actual host name as parameter to delphi executable.

Thanks

Regards
AS