Re: Gupta vs. Powerbuilder or VB

In article <jkyserCHECuH.13p_at_netcom.com> jkyser_at_netcom.com (Jeff Kyser) writes:
>umyin_at_ccu.umanitoba.ca (Qing Yin) writes:
>
>>The real issue is that PB needs the backend database at all for the extended
>>attribute. When version 3.0 comes out with built in Watcom SQL server, they
>>are saying that now you can program both at work (with Sybase for example)
>>and at home (with the built in Watcom.) I guess what they didn't tell you
>>is that, yes, you can do it as long as you don't use extended attributes.
>
>That's not the case. Version 3.0 is out, with Watcom SQL, and extended
>attibutes are supported in Watcom as well as SQL Server. The concept behind

I think he may have meant, how do you test and program at home using HOLD LOCK, BROWSE MODE and SQL Server datatypes or Transact-SQL bits outside of normal SQL against WATCOM.

>extended attributes is that they are stored closest to the data that they
>describe. So if you wanted to add attributes to Watcom data, then the
>tables would be in Watcom. Extended attributes make no sense unless related
>to the data structure in a database.
>

I'm curious. If you develop an application in server database A. You then need to move it into server database B. How do you move the 'extended attributes and validation' to the other server DBMS if you did not save any scripts?

-- 
Nigel Campbell		   Voice: (613) 738-1338 ext 3016    P.O. Box 9707
UNIX/RDBMS Marketing Mgr     FAX: (613) 738-0002             3755 Riverside Dr.
Cognos Incorporated	     MCI: nigel campbell || 3074729  Ottawa, Ontario
UUnet: nigelc_at_cognos.COM                                     CANADA  K1G 3Z4