Re: changying from ANSI mode to unbuffered logging
Yes, that what we are going to do. Recreate the database. If there are an=
y
other ways please advise.
But, the application developers worried that something might not work if =
we
changed. Any idea?? We have 4GL, stored procedures, and client PowerBuild=
er
applications.
Regards,
Nien
-----Original Message-----
From: fernando.collalti@orbit.net <fernando.collalti@orbit.net>
To: Sui <Sui>
Date: Wednesday, March 11, 1998 11:07 =E5
Subject: Re: changying from ANSI mode to unbuffered logging
>
>ANTS wrote:
>>
>> Hi all,
>>
>> We are planning to change the logging mode from ANSI to unbuffered
logging.
>> Any consequences that we have to take in 4GL, stored procedures and
>> PowerBuilder applications??
>>
>> Please advise....
>>
>> Nien
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Mails are checked daily and processed right away.
>> If you don't get my replies within 3 days please send your mail again.
>Hello,
>
>Are you sure that this can be done? Unless you execute a
>dbexport and build the database again, it is not possible to change
>loggin status from ANSI to unbuffered/buffered.
>
>
>Kind Regards.
>
>Fernando Collalti
>mail: fernando.collalti@orbit.net
>