Re: [Harbour] Visual FoxPro incompatibility

2009-04-21 Thread Adam Lubszczyk

Hi!

Massimo Belgrano-3 wrote:
 
 I have post on sybase [x]harbour newgroupI can't test because i am using
 v8
 are you using acelib,rddads created from ads v9?
 

I tested with ace32.dll, adsloc32.dll ver 7 on Windows 98SE
and ace32.dll, adsloc32.dll ver 9 on Windows XP
Sample base and index was created in VFP 6


Massimo Belgrano-3 wrote:
 
 Can you explain codepage problem?
 

Normal I use:
 REQUEST HB_CODEPAGE_PL852
 REQUEST HB_CODEPAGE_PLWIN
 HB_SETCODEPAGE(PL852)  //program and dispaly codepage
 USE base NEW CODEPAGE PLWIN  //auto translate PLWIN - PL852

In ADS: 
 USE base NEW CODEPAGE PLWIN //open but not translate

Adam
-- 
View this message in context: 
http://www.nabble.com/Visual-FoxPro-incompatibility-tp11612841p23152836.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] Visual FoxPro incompatibility

2009-04-21 Thread Massimo Belgrano
You can simply follow sybase ads newsgroup from web
http://www.nntp.hk/web/?server=devzone.advantagedatabase.com
and then click on Advantage.xHarbour
http://www.nntp.hk/web/head.php?server=devzone.advantagedatabase.comgroup=Advantage.xHarbour

2009/4/21 Adam Lubszczyk ada...@poczta.onet.pl


 Hi!

 Massimo Belgrano-3 wrote:
 
  I have post on sybase [x]harbour newgroupI can't test because i am using
  v8
  are you using acelib,rddads created from ads v9?
 

 I tested with ace32.dll, adsloc32.dll ver 7 on Windows 98SE
 and ace32.dll, adsloc32.dll ver 9 on Windows XP
 Sample base and index was created in VFP 6


 Massimo Belgrano-3 wrote:
 
  Can you explain codepage problem?
 

 Normal I use:
  REQUEST HB_CODEPAGE_PL852
  REQUEST HB_CODEPAGE_PLWIN
  HB_SETCODEPAGE(PL852)  //program and dispaly codepage
  USE base NEW CODEPAGE PLWIN  //auto translate PLWIN - PL852

 In ADS:
  USE base NEW CODEPAGE PLWIN //open but not translate

 Adam
 --
 View this message in context:
 http://www.nabble.com/Visual-FoxPro-incompatibility-tp11612841p23152836.html
 Sent from the Harbour - Dev mailing list archive at Nabble.com.

 ___
 Harbour mailing list
 Harbour@harbour-project.org
 http://lists.harbour-project.org/mailman/listinfo/harbour




-- 
Massimo Belgrano
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] Visual FoxPro incompatibility

2009-04-21 Thread Massimo Belgrano
I have post on sybase [x]harbour newgroupI can't test because i am using v8
are you using acelib,rddads created from ads v9?

Can you explain codepage problem?

2009/4/21 Adam Lubszczyk ada...@poczta.onet.pl


 Hi!

 Massimo Belgrano-3 wrote:
 
  Post a sample where you create and use table and index
  will be a problem of rddads or ads server
  you can post also to advantage news group for [x]harbour
 
 

 I do not create index - it's not problem.
 If I in ADS make index - all work OK.
 I must open existing index (only for read) maked by aplication of VFP.
 Standard Harbour DBFCDX can't open this CDX.
 ADS open this CDX and work OK except order on field type INTEGER
 ( STR(field_integer) work OK )

 Another problem with ADS is not work with CODEPAGE extension

 Sample files:  http://www.nabble.com/file/p23151376/sample.zip sample.zip

 Adam
 --
 View this message in context:
 http://www.nabble.com/Visual-FoxPro-incompatibility-tp11612841p23151376.html
 Sent from the Harbour - Dev mailing list archive at Nabble.com.

 ___
 Harbour mailing list
 Harbour@harbour-project.org
 http://lists.harbour-project.org/mailman/listinfo/harbour




-- 
Massimo Belgrano

Analisi e sviluppo software per Lan e Web - Consulenza informatica -
Formazione
Delta Informatica S.r.l. http://www.deltain.it/   +39 0321 455962
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] Visual FoxPro incompatibility

2009-04-20 Thread Adam Lubszczyk


Przemyslaw Czerpak-2 wrote:
 
 [...]
 But it's a free project and if someone is interested then he can make it.
 In such case I would like to ask to not add such functionality to core
 code
 but create new RDD in contrib.
 
 best regards,
 Przemek
 

Jesli bym potrafil, to moze bym zrobil :)
If I can, maybe I do it


Massimo Belgrano-3 wrote:
 
 Only a note
 ads v 9 use  visual fox pro 9 data and index and run in win 32-64- and
 Linux
 
  ADS9 has provided support for FoxPro tables and CDX/IDX indexes for
 a long time, ADS 9 has added full support for Visual FoxPro tables,
 including auto-increment, date/time, and VarChar fields. Advantage can
 use its proprietary, high-performance locking with Visual FoxPro
 tables, but also supports a compatibility mode, permitting legacy
 applications that access the Visual FoxPro tables directly to co-exist
 with newer, Advantage-based applications. Advantage adds the new
 ADS_VFP table type for this support.
 [...]
 
 -- 
 Massimo Belgrano
 
 

I try it.
Open Visual FoxPro CDX, but if index is on field type INTEGER not work :(

Adam

-- 
View this message in context: 
http://www.nabble.com/Visual-FoxPro-incompatibility-tp11612841p23134381.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] Visual FoxPro incompatibility

2009-04-20 Thread Massimo Belgrano
Post a sample where you create and use table and index
will be a problem of rddads or ads server
you can post also to advantage news group for [x]harbour

Thanks to the growing (x)Harbour comunity Sybase iAnyWhere has added a
new Newgroup in order to serve the (x)Harbour comunity using Advantage
Database Server.
You can join to the news group in:
news://devzone.advantagedatabase.com/Advantage.xHarbour
Use your own news reader to join


2009/4/20 Adam Lubszczyk ada...@poczta.onet.pl:

  ADS9 has provided support for FoxPro tables and CDX/IDX indexes for
 a long time, ADS 9 has added full support for Visual FoxPro tables,
 including auto-increment, date/time, and VarChar fields. Advantage can
 use its proprietary, high-performance locking with Visual FoxPro
 tables, but also supports a compatibility mode, permitting legacy
 applications that access the Visual FoxPro tables directly to co-exist
 with newer, Advantage-based applications. Advantage adds the new
 ADS_VFP table type for this support.
 [...]

 --
 I try it.
 Open Visual FoxPro CDX, but if index is on field type INTEGER not work :(

 Adam


-- 
Massimo Belgrano
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] Visual FoxPro incompatibility

2009-04-17 Thread Adam Lubszczyk

Hi Przemek, You same time ago write:

Przemyslaw Czerpak wrote:
 
 On Mon, 16 Jul 2007, Enrico Maria Giordano wrote:
 [...]
 It's not necessary. This CDX file uses Windows unicode collation function
 to hash index keys. The index key size is twice longer and is unreadable
 (check ordKeyVal()). Such indexes can be created and used only in Windows
 because MS haven't documented the collation algorithm and as usual it's
 not
 compatible with Unicode standards. So I decided to not add support for
 such
 indexes. If you need to use them in [x]Harbour then you can hack DBFCDX
 and
 hash index keys with this function but it will work only in W32 - such
 modifications should not take more then few lines.
 
 best regards,
 Przemek
 ___
 
 

Maybe You make new RDD VFP for Visual FoxPro CDX indexes as hacked DBFCDX
?

Adam

-- 
View this message in context: 
http://www.nabble.com/Visual-FoxPro-incompatibility-tp11612841p23094727.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] Visual FoxPro incompatibility

2009-04-17 Thread Przemyslaw Czerpak
On Fri, 17 Apr 2009, Adam Lubszczyk wrote:

Hi,

  It's not necessary. This CDX file uses Windows unicode collation function
  to hash index keys. The index key size is twice longer and is unreadable
  (check ordKeyVal()). Such indexes can be created and used only in Windows
  because MS haven't documented the collation algorithm and as usual it's
  not
  compatible with Unicode standards. So I decided to not add support for
  such
  indexes. If you need to use them in [x]Harbour then you can hack DBFCDX
  and
  hash index keys with this function but it will work only in W32 - such
  modifications should not take more then few lines.
 Maybe You make new RDD VFP for Visual FoxPro CDX indexes as hacked DBFCDX

But it will be still Windows only RDD which cannot be used on any other
OSes so it will only increase the gray area of strict MS binary
compatibility. Personally I do not like to take a part in such process.
But it's a free project and if someone is interested then he can make it.
In such case I would like to ask to not add such functionality to core code
but create new RDD in contrib.

best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour