Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Free DBF-tables and triggers

14 posts in FoxPro Last posting was on 2009-11-19 14:55:30.0Z
Reijo Pitkanen Posted on 2009-11-11 13:34:26.0Z
Date: Wed, 11 Nov 2009 15:34:26 +0200
From: Reijo Pitkanen <reijo.pitkanen@somermatic.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
Newsgroups: advantage.foxpro
Subject: Free DBF-tables and triggers
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 091110-1, 10.11.2009), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: 86.60.191.249
Message-ID: <4afabd04@solutions.advantagedatabase.com>
X-Trace: 11 Nov 2009 06:32:52 -0700, 86.60.191.249
Lines: 96
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!86.60.191.249
Xref: solutions.advantagedatabase.com Advantage.FoxPro:303
Article PK: 1109656

Hi,
I have been testing triggers with two simple CDX DBF-tables LEIMA.DBF
and HENKILO.DBF so that at first both tables have been dictionary tables
and after I have noticed that the trigger works I have deleted the
HENKILO-table from the dictionary and tested again.

When HENKILO is not in the dictionary ALS-server throws error :

poQuery: Error 7200: AQE Error: State = HY000; NativeError = 5177;
[iAnywhere Solutions][Advantage SQL][ASA] Error 5177: Trigger execution
failed. Error 7200: AQE Error: State = HY000; NativeError = 7010;
[iAnywhere
Solutions][Advantage SQL][ASA] Error 7010: Problem with Advantage
server file read. Table name: HENKILO.DBF ** Script error information:
-- Location of error in the SQL statement is: 186 (line: 9 column: 6)

Outside the trigger HENKILO.DBF can be accessed without problems i.e.
SELECT * FROM "HENKILO.DBF" works fine.

If I do the same thing with ADT-tables the trigger works fine also when
HENKILO.ADT table is not declared in the dictionary.

The final solution runs in remote ADS-server in Linux environment and it
is supposed to update free DBF-tables in triggers.

This is the test table having the trigger:

CREATE TABLE LEIMA (
NRO Numeric( 6 ,0 ),
NIMI Char( 50 ),
TYYPPI Numeric( 3 ,0 ),
AIKA Numeric( 10 ,0 ),
HLO Numeric( 6 ,0 )) IN DATABASE;

EXECUTE PROCEDURE sp_CreateIndex90(
'LEIMA',
'LEIMA.cdx',
'NRO',
'NRO',
'',
2,
512,
'' );

CREATE TRIGGER Uusileima
ON LEIMA
AFTER
INSERT
BEGIN
DECLARE @Kaveri Integer;
DECLARE @nimi String;
DECLARE @id Integer;
Declare curs cursor;

//Get the person ID
@Kaveri = (SELECT [hlo] from __new);
@id = (SELECT [nro] from __new);
open curs as select nimi from "HENKILO.DBF" where hlo=@kaveri;
if fetch curs then
@nimi=curs.nimi;
update "Leima.dbf" set nimi =@nimi where nro=@id;
endif;
close curs;

END
PRIORITY 1;

This is the simple table referenced from the trigger:

CREATE TABLE HENKILO (
HLO Numeric( 6 ,0 ),
NIMI Char( 50 )) IN DATABASE;
EXECUTE PROCEDURE sp_CreateIndex90(
'HENKILO',
'HENKILO.cdx',
'HLO',
'HLO',
'',
2,
512,
'' );


I am testing with ARC version is 9.10.0.11 against local server version
9.10.0.9.
Connection properties are:
-Table Type : cdx
-Server Type : local
-LockingMode: compatiple
-CharType: oem
-DBFTableType :cdx


This is a server side bug, isn't it?

Best Regards Reijo Pitkanen


Alex Wong (ADS) Posted on 2009-11-11 21:40:39.0Z
From: "Alex Wong \(ADS\)" <nobody@sybase.com>
Newsgroups: advantage.foxpro
References: <4afabd04@solutions.advantagedatabase.com>
Subject: Re: Free DBF-tables and triggers
Date: Wed, 11 Nov 2009 14:40:39 -0700
Lines: 127
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5843
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: 10.24.38.144
Message-ID: <4afb2ef8@solutions.advantagedatabase.com>
X-Trace: 11 Nov 2009 14:39:04 -0700, 10.24.38.144
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.144
Xref: solutions.advantagedatabase.com Advantage.FoxPro:304
Article PK: 1109659

Hi Reijo,

The problem here is that trigger can only use ADT free table. All SQL
scripts and queries are executed with a specific table type for free tables.
Normally, the table type is specified in the client's connection string, and
the table type sent to the server when the client executes a SQL statement.
However, when executing a trigger, the server does not have the client's
default table type and thus defaults to using the ADT table type for free
tables. When the table is part of the data dictionary, the table type (along
with other meta data about the table) is stored in the data dictionary and
the server will then be ablet to use the correct table type to open the
table.

With DBF tables, adding the table to the data dictionary does not change
anything in the table itself. It is simply a way for the data dictionary to
have the knowledge of the table. The DBF tables that are part of the data
dictionary can still be opened as free tables. The only drawback that I can
think of is when modifying the structure or index of the table while not
connected to the data dictionary, the meta data stored in the database will
be out of sync with the real table. And that can lead to some unexpected
error later on.

--
Alex

"Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
news:4afabd04@solutions.advantagedatabase.com...
> Hi,
> I have been testing triggers with two simple CDX DBF-tables LEIMA.DBF and
> HENKILO.DBF so that at first both tables have been dictionary tables and
> after I have noticed that the trigger works I have deleted the
> HENKILO-table from the dictionary and tested again.
>
> When HENKILO is not in the dictionary ALS-server throws error :
>
> poQuery: Error 7200: AQE Error: State = HY000; NativeError = 5177;
> [iAnywhere Solutions][Advantage SQL][ASA] Error 5177: Trigger execution
> failed. Error 7200: AQE Error: State = HY000; NativeError = 7010;
> [iAnywhere
> Solutions][Advantage SQL][ASA] Error 7010: Problem with Advantage server
> file read. Table name: HENKILO.DBF ** Script error information: --
> Location of error in the SQL statement is: 186 (line: 9 column: 6)
>
> Outside the trigger HENKILO.DBF can be accessed without problems i.e.
> SELECT * FROM "HENKILO.DBF" works fine.
>
> If I do the same thing with ADT-tables the trigger works fine also when
> HENKILO.ADT table is not declared in the dictionary.
>
> The final solution runs in remote ADS-server in Linux environment and it
> is supposed to update free DBF-tables in triggers.
>
> This is the test table having the trigger:
>
> CREATE TABLE LEIMA (
> NRO Numeric( 6 ,0 ),
> NIMI Char( 50 ),
> TYYPPI Numeric( 3 ,0 ),
> AIKA Numeric( 10 ,0 ),
> HLO Numeric( 6 ,0 )) IN DATABASE;
>
> EXECUTE PROCEDURE sp_CreateIndex90(
> 'LEIMA',
> 'LEIMA.cdx',
> 'NRO',
> 'NRO',
> '',
> 2,
> 512,
> '' );
>
> CREATE TRIGGER Uusileima
> ON LEIMA
> AFTER
> INSERT
> BEGIN
> DECLARE @Kaveri Integer;
> DECLARE @nimi String;
> DECLARE @id Integer;
> Declare curs cursor;
>
> //Get the person ID
> @Kaveri = (SELECT [hlo] from __new);
> @id = (SELECT [nro] from __new);
> open curs as select nimi from "HENKILO.DBF" where hlo=@kaveri;
> if fetch curs then
> @nimi=curs.nimi;
> update "Leima.dbf" set nimi =@nimi where nro=@id;
> endif;
> close curs;
>
> END
> PRIORITY 1;
>
> This is the simple table referenced from the trigger:
>
> CREATE TABLE HENKILO (
> HLO Numeric( 6 ,0 ),
> NIMI Char( 50 )) IN DATABASE;
> EXECUTE PROCEDURE sp_CreateIndex90(
> 'HENKILO',
> 'HENKILO.cdx',
> 'HLO',
> 'HLO',
> '',
> 2,
> 512,
> '' );
>
>
> I am testing with ARC version is 9.10.0.11 against local server version
> 9.10.0.9.
> Connection properties are:
> -Table Type : cdx
> -Server Type : local
> -LockingMode: compatiple
> -CharType: oem
> -DBFTableType :cdx
>
>
> This is a server side bug, isn't it?
>
> Best Regards Reijo Pitkanen


Reijo Pitkanen Posted on 2009-11-12 15:14:06.0Z
Date: Thu, 12 Nov 2009 17:14:06 +0200
From: Reijo Pitkanen <reijo.pitkanen@somermatic.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
Newsgroups: advantage.foxpro
Subject: Re: Free DBF-tables and triggers
References: <4afabd04@solutions.advantagedatabase.com> <4afb2ef8@solutions.advantagedatabase.com>
In-Reply-To: <4afb2ef8@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 091112-0, 12.11.2009), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: 86.60.191.249
Message-ID: <4afc25df@solutions.advantagedatabase.com>
X-Trace: 12 Nov 2009 08:12:31 -0700, 86.60.191.249
Lines: 142
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!86.60.191.249
Xref: solutions.advantagedatabase.com Advantage.FoxPro:305
Article PK: 1109660

Hi Alex,
Thanks for Your quick answer.

There is a small problem with CDX-index files when adding DBF-files to
the dictionary, namely Advantage assumes that index file extension is
written in lowercase (.cdx) and Foxpro makes uppercase index-files.
I could change all index file extensions to lowercase, but if someone
does reindex the table with foxpro, it changes the index file extension
to uppercase and the table can not be opened any more with ADS.
This is not a problem in Windows environment, but in Linux it sure is.
--
Reijo

Alex Wong (ADS) wrote:
> Hi Reijo,
>
> The problem here is that trigger can only use ADT free table. All SQL
> scripts and queries are executed with a specific table type for free tables.
> Normally, the table type is specified in the client's connection string, and
> the table type sent to the server when the client executes a SQL statement.
> However, when executing a trigger, the server does not have the client's
> default table type and thus defaults to using the ADT table type for free
> tables. When the table is part of the data dictionary, the table type (along
> with other meta data about the table) is stored in the data dictionary and
> the server will then be ablet to use the correct table type to open the
> table.
>
> With DBF tables, adding the table to the data dictionary does not change
> anything in the table itself. It is simply a way for the data dictionary to
> have the knowledge of the table. The DBF tables that are part of the data
> dictionary can still be opened as free tables. The only drawback that I can
> think of is when modifying the structure or index of the table while not
> connected to the data dictionary, the meta data stored in the database will
> be out of sync with the real table. And that can lead to some unexpected
> error later on.
>
> --
> Alex
>
>
>
> "Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
> news:4afabd04@solutions.advantagedatabase.com...
>> Hi,
>> I have been testing triggers with two simple CDX DBF-tables LEIMA.DBF and
>> HENKILO.DBF so that at first both tables have been dictionary tables and
>> after I have noticed that the trigger works I have deleted the
>> HENKILO-table from the dictionary and tested again.
>>
>> When HENKILO is not in the dictionary ALS-server throws error :
>>
>> poQuery: Error 7200: AQE Error: State = HY000; NativeError = 5177;
>> [iAnywhere Solutions][Advantage SQL][ASA] Error 5177: Trigger execution
>> failed. Error 7200: AQE Error: State = HY000; NativeError = 7010;
>> [iAnywhere
>> Solutions][Advantage SQL][ASA] Error 7010: Problem with Advantage server
>> file read. Table name: HENKILO.DBF ** Script error information: --
>> Location of error in the SQL statement is: 186 (line: 9 column: 6)
>>
>> Outside the trigger HENKILO.DBF can be accessed without problems i.e.
>> SELECT * FROM "HENKILO.DBF" works fine.
>>
>> If I do the same thing with ADT-tables the trigger works fine also when
>> HENKILO.ADT table is not declared in the dictionary.
>>
>> The final solution runs in remote ADS-server in Linux environment and it
>> is supposed to update free DBF-tables in triggers.
>>
>> This is the test table having the trigger:
>>
>> CREATE TABLE LEIMA (
>> NRO Numeric( 6 ,0 ),
>> NIMI Char( 50 ),
>> TYYPPI Numeric( 3 ,0 ),
>> AIKA Numeric( 10 ,0 ),
>> HLO Numeric( 6 ,0 )) IN DATABASE;
>>
>> EXECUTE PROCEDURE sp_CreateIndex90(
>> 'LEIMA',
>> 'LEIMA.cdx',
>> 'NRO',
>> 'NRO',
>> '',
>> 2,
>> 512,
>> '' );
>>
>> CREATE TRIGGER Uusileima
>> ON LEIMA
>> AFTER
>> INSERT
>> BEGIN
>> DECLARE @Kaveri Integer;
>> DECLARE @nimi String;
>> DECLARE @id Integer;
>> Declare curs cursor;
>>
>> //Get the person ID
>> @Kaveri = (SELECT [hlo] from __new);
>> @id = (SELECT [nro] from __new);
>> open curs as select nimi from "HENKILO.DBF" where hlo=@kaveri;
>> if fetch curs then
>> @nimi=curs.nimi;
>> update "Leima.dbf" set nimi =@nimi where nro=@id;
>> endif;
>> close curs;
>>
>> END
>> PRIORITY 1;
>>
>> This is the simple table referenced from the trigger:
>>
>> CREATE TABLE HENKILO (
>> HLO Numeric( 6 ,0 ),
>> NIMI Char( 50 )) IN DATABASE;
>> EXECUTE PROCEDURE sp_CreateIndex90(
>> 'HENKILO',
>> 'HENKILO.cdx',
>> 'HLO',
>> 'HLO',
>> '',
>> 2,
>> 512,
>> '' );
>>
>>
>> I am testing with ARC version is 9.10.0.11 against local server version
>> 9.10.0.9.
>> Connection properties are:
>> -Table Type : cdx
>> -Server Type : local
>> -LockingMode: compatiple
>> -CharType: oem
>> -DBFTableType :cdx
>>
>>
>> This is a server side bug, isn't it?
>>
>> Best Regards Reijo Pitkanen
>
>


Joachim Duerr (ADS) Posted on 2009-11-12 15:22:08.0Z
From: "Joachim Duerr (ADS)" <jojo.duerr@gmx.de>
Subject: Re: Free DBF-tables and triggers
Newsgroups: Advantage.FoxPro
References: <4afabd04@solutions.advantagedatabase.com> <4afb2ef8@solutions.advantagedatabase.com> <4afc25df@solutions.advantagedatabase.com>
Date: Thu, 12 Nov 2009 16:22:08 +0100
User-Agent: XanaNews/1.19.1.194
X-Face: u2p+</,mb|Ah!x!/qxX5q0t:O~.<1&JzwNHYhSqcviY{~&|iDc"U.Je1A.ZeHR`d;;y#R
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
NNTP-Posting-Host: 79.221.71.139
Message-ID: <4afc27bd@solutions.advantagedatabase.com>
X-Trace: 12 Nov 2009 08:20:29 -0700, 79.221.71.139
Lines: 19
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!79.221.71.139
Xref: solutions.advantagedatabase.com Advantage.FoxPro:306
Article PK: 1109658


Reijo Pitkanen wrote:

>There is a small problem with CDX-index files when adding DBF-files
>to the dictionary, namely Advantage assumes that index file extension
>is written in lowercase (.cdx) and Foxpro makes uppercase
>index-files. I could change all index file extensions to lowercase,
>but if someone does reindex the table with foxpro, it changes the
>index file extension to uppercase and the table can not be opened any
>more with ADS. This is not a problem in Windows environment, but in
>Linux it sure is.

to avoid this on linux, set
LOWERCASE_ALL_PATHS=1
in the ads.conf.

--
Joachim Duerr
Advantage Presales
check out my new ADS book on http://www.jd-engineering.de/adsbuch


Reijo Pitkanen Posted on 2009-11-13 05:46:37.0Z
Date: Fri, 13 Nov 2009 07:46:37 +0200
From: Reijo Pitkanen <reijo.pitkanen@somermatic.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
Newsgroups: Advantage.FoxPro
Subject: Re: Free DBF-tables and triggers
References: <4afabd04@solutions.advantagedatabase.com> <4afb2ef8@solutions.advantagedatabase.com> <4afc25df@solutions.advantagedatabase.com> <4afc27bd@solutions.advantagedatabase.com>
In-Reply-To: <4afc27bd@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 091112-1, 12.11.2009), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: 86.60.191.249
Message-ID: <4afcf25c@solutions.advantagedatabase.com>
X-Trace: 12 Nov 2009 22:45:00 -0700, 86.60.191.249
Lines: 22
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!86.60.191.249
Xref: solutions.advantagedatabase.com Advantage.FoxPro:307
Article PK: 1109661

Yes Joachim, but this does not solve the problem because foxpro turns
the file name to UPPERCASE when reindexing, and we are in the same
situation where ADS does not find the index file.

- Reijo

Joachim Duerr (ADS) wrote:
> Reijo Pitkanen wrote:
>
>> There is a small problem with CDX-index files when adding DBF-files
>> to the dictionary, namely Advantage assumes that index file extension
>> is written in lowercase (.cdx) and Foxpro makes uppercase
>> index-files. I could change all index file extensions to lowercase,
>> but if someone does reindex the table with foxpro, it changes the
>> index file extension to uppercase and the table can not be opened any
>> more with ADS. This is not a problem in Windows environment, but in
>> Linux it sure is.
>
> to avoid this on linux, set
> LOWERCASE_ALL_PATHS=1
> in the ads.conf.
>


Joachim Duerr (ADS) Posted on 2009-11-13 11:09:52.0Z
From: "Joachim Duerr (ADS)" <jojo.duerr@gmx.de>
Subject: Re: Free DBF-tables and triggers
Newsgroups: Advantage.FoxPro
References: <4afabd04@solutions.advantagedatabase.com> <4afb2ef8@solutions.advantagedatabase.com> <4afc25df@solutions.advantagedatabase.com> <4afc27bd@solutions.advantagedatabase.com> <4afcf25c@solutions.advantagedatabase.com>
Date: Fri, 13 Nov 2009 12:09:52 +0100
User-Agent: XanaNews/1.19.1.194
X-Face: u2p+</,mb|Ah!x!/qxX5q0t:O~.<1&JzwNHYhSqcviY{~&|iDc"U.Je1A.ZeHR`d;;y#R
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
NNTP-Posting-Host: 79.221.114.74
Message-ID: <4afd3e1d@solutions.advantagedatabase.com>
X-Trace: 13 Nov 2009 04:08:13 -0700, 79.221.114.74
Lines: 14
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!79.221.114.74
Xref: solutions.advantagedatabase.com Advantage.FoxPro:308
Article PK: 1109662


Reijo Pitkanen wrote:

>
>Yes Joachim, but this does not solve the problem because foxpro turns
>the file name to UPPERCASE when reindexing, and we are in the same
>situation where ADS does not find the index file.

for direct accessing the files on the linux box, you should set up
Samba to use lowercase only.

--
Joachim Duerr
Advantage Presales
check out my new ADS book on http://www.jd-engineering.de/adsbuch


Reijo Pitkanen Posted on 2009-11-13 17:29:35.0Z
Date: Fri, 13 Nov 2009 19:29:35 +0200
From: Reijo Pitkanen <reijo.pitkanen@somermatic.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
Newsgroups: Advantage.FoxPro
Subject: Re: Free DBF-tables and triggers
References: <4afabd04@solutions.advantagedatabase.com> <4afb2ef8@solutions.advantagedatabase.com> <4afc25df@solutions.advantagedatabase.com> <4afc27bd@solutions.advantagedatabase.com> <4afcf25c@solutions.advantagedatabase.com> <4afd3e1d@solutions.advantagedatabase.com>
In-Reply-To: <4afd3e1d@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 091113-0, 13.11.2009), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: 86.60.191.249
Message-ID: <4afd971e@solutions.advantagedatabase.com>
X-Trace: 13 Nov 2009 10:27:58 -0700, 86.60.191.249
Lines: 17
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!86.60.191.249
Xref: solutions.advantagedatabase.com Advantage.FoxPro:309
Article PK: 1109663

I would rather keep Samba settings in their default values.

Is it too difficult to preserve the case in filenames and/or give the
user the ability to edit index file names in the dictionary?

- Reijo

Joachim Duerr (ADS) wrote:
> Reijo Pitkanen wrote:
>
>> Yes Joachim, but this does not solve the problem because foxpro turns
>> the file name to UPPERCASE when reindexing, and we are in the same
>> situation where ADS does not find the index file.
>
> for direct accessing the files on the linux box, you should set up
> Samba to use lowercase only.
>


Alex Wong (ADS) Posted on 2009-11-13 20:27:07.0Z
From: "Alex Wong \(ADS\)" <nobody@sybase.com>
Newsgroups: Advantage.FoxPro
References: <4afabd04@solutions.advantagedatabase.com> <4afb2ef8@solutions.advantagedatabase.com> <4afc25df@solutions.advantagedatabase.com> <4afc27bd@solutions.advantagedatabase.com> <4afcf25c@solutions.advantagedatabase.com> <4afd3e1d@solutions.advantagedatabase.com> <4afd971e@solutions.advantagedatabase.com>
Subject: Re: Free DBF-tables and triggers
Date: Fri, 13 Nov 2009 13:27:07 -0700
Lines: 38
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5843
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: 10.24.38.144
Message-ID: <4afdc0bb@solutions.advantagedatabase.com>
X-Trace: 13 Nov 2009 13:25:31 -0700, 10.24.38.144
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.144
Xref: solutions.advantagedatabase.com Advantage.FoxPro:310
Article PK: 1109664

Advantage does not assume the name is lower case, unless the
LOWERCASE_ALL_PATHS is true.

The data dictionary preserve the case of the index file name at the time the
table and index were added to the data dictionary. If you create the index
in Advantage using ALL UPPER case, then there should be no problem when the
file is re-indexed by FoxPro. Make sure that you do not set the
LOWERCASE_ALL_PATHS to true when creating the index.

You can see the index file names (with the preserved case) by executing the
following query in ARC - SELECT * FROM system.indexfiles.

--
Alex

"Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
news:4afd971e@solutions.advantagedatabase.com...
>I would rather keep Samba settings in their default values.
>
> Is it too difficult to preserve the case in filenames and/or give the user
> the ability to edit index file names in the dictionary?
>
> - Reijo
>
> Joachim Duerr (ADS) wrote:
>> Reijo Pitkanen wrote:
>>
>>> Yes Joachim, but this does not solve the problem because foxpro turns
>>> the file name to UPPERCASE when reindexing, and we are in the same
>>> situation where ADS does not find the index file.
>>
>> for direct accessing the files on the linux box, you should set up
>> Samba to use lowercase only.
>>


Reijo Pitkanen Posted on 2009-11-14 11:29:14.0Z
Date: Sat, 14 Nov 2009 13:29:14 +0200
From: Reijo Pitkanen <reijo.pitkanen@somermatic.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
Newsgroups: Advantage.FoxPro
Subject: Re: Free DBF-tables and triggers
References: <4afabd04@solutions.advantagedatabase.com> <4afb2ef8@solutions.advantagedatabase.com> <4afc25df@solutions.advantagedatabase.com> <4afc27bd@solutions.advantagedatabase.com> <4afcf25c@solutions.advantagedatabase.com> <4afd3e1d@solutions.advantagedatabase.com> <4afd971e@solutions.advantagedatabase.com> <4afdc0bb@solutions.advantagedatabase.com>
In-Reply-To: <4afdc0bb@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 091114-0, 14.11.2009), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: 86.60.191.249
Message-ID: <4afe942a@solutions.advantagedatabase.com>
X-Trace: 14 Nov 2009 04:27:38 -0700, 86.60.191.249
Lines: 59
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!86.60.191.249
Xref: solutions.advantagedatabase.com Advantage.FoxPro:311
Article PK: 1109665

When I add DBF-tables to dictionary with ARC, it accepts the table, but
when you try to open it you get error messages:

BrowseTable: Error 7041: File not found. Verify the specified path and
file name is correct..

When you look table properties with arc, the table name is correct
uppercase, but the index file name has lowercase extension.
For example according to ARC's table properties dialog the table
ASIAKAS.DBF should have index file ASIAKAS.cdx.
On Linux file system the index filename is ASIAKAS.CDX.
I can open the table without any problems, if I rename the index file so
that it has lowercase extension (ASIAKAS.cdx).

Also the Query SELECT * FROM system.indexfiles gives all index filenames
with lowercase extension.
Conclusion: the "Add existing table(s)" function in ARC has a small bug,
hasn't it?
--
Reijo

Alex Wong (ADS) wrote:
> Advantage does not assume the name is lower case, unless the
> LOWERCASE_ALL_PATHS is true.
>
> The data dictionary preserve the case of the index file name at the time the
> table and index were added to the data dictionary. If you create the index
> in Advantage using ALL UPPER case, then there should be no problem when the
> file is re-indexed by FoxPro. Make sure that you do not set the
> LOWERCASE_ALL_PATHS to true when creating the index.
>
> You can see the index file names (with the preserved case) by executing the
> following query in ARC - SELECT * FROM system.indexfiles.
>
> --
> Alex
>
>
>
> "Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
> news:4afd971e@solutions.advantagedatabase.com...
>> I would rather keep Samba settings in their default values.
>>
>> Is it too difficult to preserve the case in filenames and/or give the user
>> the ability to edit index file names in the dictionary?
>>
>> - Reijo
>>
>> Joachim Duerr (ADS) wrote:
>>> Reijo Pitkanen wrote:
>>>
>>>> Yes Joachim, but this does not solve the problem because foxpro turns
>>>> the file name to UPPERCASE when reindexing, and we are in the same
>>>> situation where ADS does not find the index file.
>>> for direct accessing the files on the linux box, you should set up
>>> Samba to use lowercase only.
>>>
>
>


Alex Wong (ADS) Posted on 2009-11-16 23:24:47.0Z
From: "Alex Wong \(ADS\)" <nobody@sybase.com>
Newsgroups: Advantage.FoxPro
References: <4afabd04@solutions.advantagedatabase.com> <4afb2ef8@solutions.advantagedatabase.com> <4afc25df@solutions.advantagedatabase.com> <4afc27bd@solutions.advantagedatabase.com> <4afcf25c@solutions.advantagedatabase.com> <4afd3e1d@solutions.advantagedatabase.com> <4afd971e@solutions.advantagedatabase.com> <4afdc0bb@solutions.advantagedatabase.com> <4afe942a@solutions.advantagedatabase.com>
Subject: Re: Free DBF-tables and triggers
Date: Mon, 16 Nov 2009 16:24:47 -0700
Lines: 86
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 10.24.38.144
Message-ID: <4b01dede@solutions.advantagedatabase.com>
X-Trace: 16 Nov 2009 16:23:10 -0700, 10.24.38.144
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.144
Xref: solutions.advantagedatabase.com Advantage.FoxPro:313
Article PK: 1109666

I see the problem. It is not a ARC problem per se. The server has something
to do with it as well. When a table is being added to the data dictionary,
and there is an autoopen index available, the server will open the index
using the base table name and the lower cased extension to open the index
file. It is simly making a guess and works fine in Windows environment. The
server has no knowledge what the case should be. If the index is opened
successfully, as in the case of Windows, the file name used to open the
index will be stored in the data dictionary.

If my theory is correct, then if the data dictionary on the Linux server
when adding the table to the data dictionary, then an index file with UPPER
CASE extension would not be added to the data dictionary. You can then
manually add the index file to the data dictionary and make it associate
with the table. That may work.

I think the easiest way to work around this problem is to keep all file with
lower cased names. After reindexing the tables in FoxPro, run a routine to
make sure that all files has lower case names. It is simply one of the
problems that needed to be taken care of when using mixed Windows and Linux
environment.

--
Alex

"Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
news:4afe942a@solutions.advantagedatabase.com...
> When I add DBF-tables to dictionary with ARC, it accepts the table, but
> when you try to open it you get error messages:
>
> BrowseTable: Error 7041: File not found. Verify the specified path and
> file name is correct..
>
> When you look table properties with arc, the table name is correct
> uppercase, but the index file name has lowercase extension.
> For example according to ARC's table properties dialog the table
> ASIAKAS.DBF should have index file ASIAKAS.cdx.
> On Linux file system the index filename is ASIAKAS.CDX.
> I can open the table without any problems, if I rename the index file so
> that it has lowercase extension (ASIAKAS.cdx).
>
> Also the Query SELECT * FROM system.indexfiles gives all index filenames
> with lowercase extension.
> Conclusion: the "Add existing table(s)" function in ARC has a small bug,
> hasn't it?
> --
> Reijo
>
> Alex Wong (ADS) wrote:
>> Advantage does not assume the name is lower case, unless the
>> LOWERCASE_ALL_PATHS is true.
>>
>> The data dictionary preserve the case of the index file name at the time
>> the table and index were added to the data dictionary. If you create the
>> index in Advantage using ALL UPPER case, then there should be no problem
>> when the file is re-indexed by FoxPro. Make sure that you do not set the
>> LOWERCASE_ALL_PATHS to true when creating the index.
>>
>> You can see the index file names (with the preserved case) by executing
>> the following query in ARC - SELECT * FROM system.indexfiles.
>>
>> --
>> Alex
>>
>>
>>
>> "Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
>> news:4afd971e@solutions.advantagedatabase.com...
>>> I would rather keep Samba settings in their default values.
>>>
>>> Is it too difficult to preserve the case in filenames and/or give the
>>> user the ability to edit index file names in the dictionary?
>>>
>>> - Reijo
>>>
>>> Joachim Duerr (ADS) wrote:
>>>> Reijo Pitkanen wrote:
>>>>
>>>>> Yes Joachim, but this does not solve the problem because foxpro turns
>>>>> the file name to UPPERCASE when reindexing, and we are in the same
>>>>> situation where ADS does not find the index file.
>>>> for direct accessing the files on the linux box, you should set up
>>>> Samba to use lowercase only.
>>>>
>>


Reijo Pitkanen Posted on 2009-11-17 05:58:37.0Z
Date: Tue, 17 Nov 2009 07:58:37 +0200
From: Reijo Pitkanen <reijo.pitkanen@somermatic.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
Newsgroups: Advantage.FoxPro
Subject: Re: Free DBF-tables and triggers
References: <4afabd04@solutions.advantagedatabase.com> <4afb2ef8@solutions.advantagedatabase.com> <4afc25df@solutions.advantagedatabase.com> <4afc27bd@solutions.advantagedatabase.com> <4afcf25c@solutions.advantagedatabase.com> <4afd3e1d@solutions.advantagedatabase.com> <4afd971e@solutions.advantagedatabase.com> <4afdc0bb@solutions.advantagedatabase.com> <4afe942a@solutions.advantagedatabase.com> <4b01dede@solutions.advantagedatabase.com>
In-Reply-To: <4b01dede@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 091116-1, 16.11.2009), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: 86.60.191.249
Message-ID: <4b023b2c@solutions.advantagedatabase.com>
X-Trace: 16 Nov 2009 22:57:00 -0700, 86.60.191.249
Lines: 96
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!86.60.191.249
Xref: solutions.advantagedatabase.com Advantage.FoxPro:314
Article PK: 1109668

The auto open index file name is added to the dictionary with lower case
extension though there is no such file, and I doubt that Advantage does
not allow to add the same index file again with uppercase extension to
the dictionary.

Would it bee a big change to use the same case with index file that the
base table has?
--
Reijo

Alex Wong (ADS) wrote:
> I see the problem. It is not a ARC problem per se. The server has something
> to do with it as well. When a table is being added to the data dictionary,
> and there is an autoopen index available, the server will open the index
> using the base table name and the lower cased extension to open the index
> file. It is simly making a guess and works fine in Windows environment. The
> server has no knowledge what the case should be. If the index is opened
> successfully, as in the case of Windows, the file name used to open the
> index will be stored in the data dictionary.
>
> If my theory is correct, then if the data dictionary on the Linux server
> when adding the table to the data dictionary, then an index file with UPPER
> CASE extension would not be added to the data dictionary. You can then
> manually add the index file to the data dictionary and make it associate
> with the table. That may work.
>
> I think the easiest way to work around this problem is to keep all file with
> lower cased names. After reindexing the tables in FoxPro, run a routine to
> make sure that all files has lower case names. It is simply one of the
> problems that needed to be taken care of when using mixed Windows and Linux
> environment.
>
> --
> Alex
>
>
> "Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
> news:4afe942a@solutions.advantagedatabase.com...
>> When I add DBF-tables to dictionary with ARC, it accepts the table, but
>> when you try to open it you get error messages:
>>
>> BrowseTable: Error 7041: File not found. Verify the specified path and
>> file name is correct..
>>
>> When you look table properties with arc, the table name is correct
>> uppercase, but the index file name has lowercase extension.
>> For example according to ARC's table properties dialog the table
>> ASIAKAS.DBF should have index file ASIAKAS.cdx.
>> On Linux file system the index filename is ASIAKAS.CDX.
>> I can open the table without any problems, if I rename the index file so
>> that it has lowercase extension (ASIAKAS.cdx).
>>
>> Also the Query SELECT * FROM system.indexfiles gives all index filenames
>> with lowercase extension.
>> Conclusion: the "Add existing table(s)" function in ARC has a small bug,
>> hasn't it?
>> --
>> Reijo
>>
>> Alex Wong (ADS) wrote:
>>> Advantage does not assume the name is lower case, unless the
>>> LOWERCASE_ALL_PATHS is true.
>>>
>>> The data dictionary preserve the case of the index file name at the time
>>> the table and index were added to the data dictionary. If you create the
>>> index in Advantage using ALL UPPER case, then there should be no problem
>>> when the file is re-indexed by FoxPro. Make sure that you do not set the
>>> LOWERCASE_ALL_PATHS to true when creating the index.
>>>
>>> You can see the index file names (with the preserved case) by executing
>>> the following query in ARC - SELECT * FROM system.indexfiles.
>>>
>>> --
>>> Alex
>>>
>>>
>>>
>>> "Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
>>> news:4afd971e@solutions.advantagedatabase.com...
>>>> I would rather keep Samba settings in their default values.
>>>>
>>>> Is it too difficult to preserve the case in filenames and/or give the
>>>> user the ability to edit index file names in the dictionary?
>>>>
>>>> - Reijo
>>>>
>>>> Joachim Duerr (ADS) wrote:
>>>>> Reijo Pitkanen wrote:
>>>>>
>>>>>> Yes Joachim, but this does not solve the problem because foxpro turns
>>>>>> the file name to UPPERCASE when reindexing, and we are in the same
>>>>>> situation where ADS does not find the index file.
>>>>> for direct accessing the files on the linux box, you should set up
>>>>> Samba to use lowercase only.
>>>>>
>


Alex Wong (ADS) Posted on 2009-11-17 21:23:34.0Z
From: "Alex Wong \(ADS\)" <nobody@sybase.com>
Newsgroups: Advantage.FoxPro
References: <4afabd04@solutions.advantagedatabase.com> <4afb2ef8@solutions.advantagedatabase.com> <4afc25df@solutions.advantagedatabase.com> <4afc27bd@solutions.advantagedatabase.com> <4afcf25c@solutions.advantagedatabase.com> <4afd3e1d@solutions.advantagedatabase.com> <4afd971e@solutions.advantagedatabase.com> <4afdc0bb@solutions.advantagedatabase.com> <4afe942a@solutions.advantagedatabase.com> <4b01dede@solutions.advantagedatabase.com> <4b023b2c@solutions.advantagedatabase.com>
Subject: Re: Free DBF-tables and triggers
Date: Tue, 17 Nov 2009 14:23:34 -0700
Lines: 122
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5843
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: 10.24.38.144
Message-ID: <4b0313f4@solutions.advantagedatabase.com>
X-Trace: 17 Nov 2009 14:21:56 -0700, 10.24.38.144
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.144
Xref: solutions.advantagedatabase.com Advantage.FoxPro:321
Article PK: 1109676

With help from our Linux guru, we did some test on this and confirm your
finding. This appears to be a bug and we will have it fixed in the next
update. In the mean time, there is a rather convoluted workaround.

1. Move the index file away from the directory.
2. Add the table to the data dictionary. The index file will not be added to
the table.
3. Move the index file back into the directory and then execute the
following command in the SQL Windows:

EXECUTE PROCEDURE sp_AddIndexFileToDatabase( 'MYTABLE', 'MYTABLE.CDX',
NULL );

This should preserve the case of the file name in the data dictionary.

--
Alex

"Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
news:4b023b2c@solutions.advantagedatabase.com...
> The auto open index file name is added to the dictionary with lower case
> extension though there is no such file, and I doubt that Advantage does
> not allow to add the same index file again with uppercase extension to the
> dictionary.
>
> Would it bee a big change to use the same case with index file that the
> base table has?
> --
> Reijo
>
> Alex Wong (ADS) wrote:
>> I see the problem. It is not a ARC problem per se. The server has
>> something to do with it as well. When a table is being added to the data
>> dictionary, and there is an autoopen index available, the server will
>> open the index using the base table name and the lower cased extension to
>> open the index file. It is simly making a guess and works fine in Windows
>> environment. The server has no knowledge what the case should be. If the
>> index is opened successfully, as in the case of Windows, the file name
>> used to open the index will be stored in the data dictionary.
>>
>> If my theory is correct, then if the data dictionary on the Linux server
>> when adding the table to the data dictionary, then an index file with
>> UPPER CASE extension would not be added to the data dictionary. You can
>> then manually add the index file to the data dictionary and make it
>> associate with the table. That may work.
>>
>> I think the easiest way to work around this problem is to keep all file
>> with lower cased names. After reindexing the tables in FoxPro, run a
>> routine to make sure that all files has lower case names. It is simply
>> one of the problems that needed to be taken care of when using mixed
>> Windows and Linux environment.
>>
>> --
>> Alex
>>
>>
>> "Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
>> news:4afe942a@solutions.advantagedatabase.com...
>>> When I add DBF-tables to dictionary with ARC, it accepts the table, but
>>> when you try to open it you get error messages:
>>>
>>> BrowseTable: Error 7041: File not found. Verify the specified path and
>>> file name is correct..
>>>
>>> When you look table properties with arc, the table name is correct
>>> uppercase, but the index file name has lowercase extension.
>>> For example according to ARC's table properties dialog the table
>>> ASIAKAS.DBF should have index file ASIAKAS.cdx.
>>> On Linux file system the index filename is ASIAKAS.CDX.
>>> I can open the table without any problems, if I rename the index file so
>>> that it has lowercase extension (ASIAKAS.cdx).
>>>
>>> Also the Query SELECT * FROM system.indexfiles gives all index filenames
>>> with lowercase extension.
>>> Conclusion: the "Add existing table(s)" function in ARC has a small bug,
>>> hasn't it?
>>> --
>>> Reijo
>>>
>>> Alex Wong (ADS) wrote:
>>>> Advantage does not assume the name is lower case, unless the
>>>> LOWERCASE_ALL_PATHS is true.
>>>>
>>>> The data dictionary preserve the case of the index file name at the
>>>> time the table and index were added to the data dictionary. If you
>>>> create the index in Advantage using ALL UPPER case, then there should
>>>> be no problem when the file is re-indexed by FoxPro. Make sure that you
>>>> do not set the LOWERCASE_ALL_PATHS to true when creating the index.
>>>>
>>>> You can see the index file names (with the preserved case) by executing
>>>> the following query in ARC - SELECT * FROM system.indexfiles.
>>>>
>>>> --
>>>> Alex
>>>>
>>>>
>>>>
>>>> "Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
>>>> news:4afd971e@solutions.advantagedatabase.com...
>>>>> I would rather keep Samba settings in their default values.
>>>>>
>>>>> Is it too difficult to preserve the case in filenames and/or give the
>>>>> user the ability to edit index file names in the dictionary?
>>>>>
>>>>> - Reijo
>>>>>
>>>>> Joachim Duerr (ADS) wrote:
>>>>>> Reijo Pitkanen wrote:
>>>>>>
>>>>>>> Yes Joachim, but this does not solve the problem because foxpro
>>>>>>> turns
>>>>>>> the file name to UPPERCASE when reindexing, and we are in the same
>>>>>>> situation where ADS does not find the index file.
>>>>>> for direct accessing the files on the linux box, you should set up
>>>>>> Samba to use lowercase only.
>>>>>>
>>


Reijo Pitkanen Posted on 2009-11-19 14:55:30.0Z
Date: Thu, 19 Nov 2009 16:55:30 +0200
From: Reijo Pitkanen <reijo.pitkanen@somermatic.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
Newsgroups: Advantage.FoxPro
Subject: Re: Free DBF-tables and triggers
References: <4afabd04@solutions.advantagedatabase.com> <4afb2ef8@solutions.advantagedatabase.com> <4afc25df@solutions.advantagedatabase.com> <4afc27bd@solutions.advantagedatabase.com> <4afcf25c@solutions.advantagedatabase.com> <4afd3e1d@solutions.advantagedatabase.com> <4afd971e@solutions.advantagedatabase.com> <4afdc0bb@solutions.advantagedatabase.com> <4afe942a@solutions.advantagedatabase.com> <4b01dede@solutions.advantagedatabase.com> <4b023b2c@solutions.advantagedatabase.com> <4b0313f4@solutions.advantagedatabase.com>
In-Reply-To: <4b0313f4@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 091119-1, 19.11.2009), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: 86.60.191.249
Message-ID: <4b055c02@solutions.advantagedatabase.com>
X-Trace: 19 Nov 2009 07:53:54 -0700, 86.60.191.249
Lines: 127
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!86.60.191.249
Xref: solutions.advantagedatabase.com Advantage.FoxPro:325
Article PK: 1109679

Thanks Alex,
Your workaround solves this problem.
-
Reijo

Alex Wong (ADS) wrote:
> With help from our Linux guru, we did some test on this and confirm your
> finding. This appears to be a bug and we will have it fixed in the next
> update. In the mean time, there is a rather convoluted workaround.
>
> 1. Move the index file away from the directory.
> 2. Add the table to the data dictionary. The index file will not be added to
> the table.
> 3. Move the index file back into the directory and then execute the
> following command in the SQL Windows:
>
> EXECUTE PROCEDURE sp_AddIndexFileToDatabase( 'MYTABLE', 'MYTABLE.CDX',
> NULL );
>
> This should preserve the case of the file name in the data dictionary.
>
> --
> Alex
>
>
>
>
> "Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
> news:4b023b2c@solutions.advantagedatabase.com...
>> The auto open index file name is added to the dictionary with lower case
>> extension though there is no such file, and I doubt that Advantage does
>> not allow to add the same index file again with uppercase extension to the
>> dictionary.
>>
>> Would it bee a big change to use the same case with index file that the
>> base table has?
>> --
>> Reijo
>>
>> Alex Wong (ADS) wrote:
>>> I see the problem. It is not a ARC problem per se. The server has
>>> something to do with it as well. When a table is being added to the data
>>> dictionary, and there is an autoopen index available, the server will
>>> open the index using the base table name and the lower cased extension to
>>> open the index file. It is simly making a guess and works fine in Windows
>>> environment. The server has no knowledge what the case should be. If the
>>> index is opened successfully, as in the case of Windows, the file name
>>> used to open the index will be stored in the data dictionary.
>>>
>>> If my theory is correct, then if the data dictionary on the Linux server
>>> when adding the table to the data dictionary, then an index file with
>>> UPPER CASE extension would not be added to the data dictionary. You can
>>> then manually add the index file to the data dictionary and make it
>>> associate with the table. That may work.
>>>
>>> I think the easiest way to work around this problem is to keep all file
>>> with lower cased names. After reindexing the tables in FoxPro, run a
>>> routine to make sure that all files has lower case names. It is simply
>>> one of the problems that needed to be taken care of when using mixed
>>> Windows and Linux environment.
>>>
>>> --
>>> Alex
>>>
>>>
>>> "Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
>>> news:4afe942a@solutions.advantagedatabase.com...
>>>> When I add DBF-tables to dictionary with ARC, it accepts the table, but
>>>> when you try to open it you get error messages:
>>>>
>>>> BrowseTable: Error 7041: File not found. Verify the specified path and
>>>> file name is correct..
>>>>
>>>> When you look table properties with arc, the table name is correct
>>>> uppercase, but the index file name has lowercase extension.
>>>> For example according to ARC's table properties dialog the table
>>>> ASIAKAS.DBF should have index file ASIAKAS.cdx.
>>>> On Linux file system the index filename is ASIAKAS.CDX.
>>>> I can open the table without any problems, if I rename the index file so
>>>> that it has lowercase extension (ASIAKAS.cdx).
>>>>
>>>> Also the Query SELECT * FROM system.indexfiles gives all index filenames
>>>> with lowercase extension.
>>>> Conclusion: the "Add existing table(s)" function in ARC has a small bug,
>>>> hasn't it?
>>>> --
>>>> Reijo
>>>>
>>>> Alex Wong (ADS) wrote:
>>>>> Advantage does not assume the name is lower case, unless the
>>>>> LOWERCASE_ALL_PATHS is true.
>>>>>
>>>>> The data dictionary preserve the case of the index file name at the
>>>>> time the table and index were added to the data dictionary. If you
>>>>> create the index in Advantage using ALL UPPER case, then there should
>>>>> be no problem when the file is re-indexed by FoxPro. Make sure that you
>>>>> do not set the LOWERCASE_ALL_PATHS to true when creating the index.
>>>>>
>>>>> You can see the index file names (with the preserved case) by executing
>>>>> the following query in ARC - SELECT * FROM system.indexfiles.
>>>>>
>>>>> --
>>>>> Alex
>>>>>
>>>>>
>>>>>
>>>>> "Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
>>>>> news:4afd971e@solutions.advantagedatabase.com...
>>>>>> I would rather keep Samba settings in their default values.
>>>>>>
>>>>>> Is it too difficult to preserve the case in filenames and/or give the
>>>>>> user the ability to edit index file names in the dictionary?
>>>>>>
>>>>>> - Reijo
>>>>>>
>>>>>> Joachim Duerr (ADS) wrote:
>>>>>>> Reijo Pitkanen wrote:
>>>>>>>
>>>>>>>> Yes Joachim, but this does not solve the problem because foxpro
>>>>>>>> turns
>>>>>>>> the file name to UPPERCASE when reindexing, and we are in the same
>>>>>>>> situation where ADS does not find the index file.
>>>>>>> for direct accessing the files on the linux box, you should set up
>>>>>>> Samba to use lowercase only.
>>>>>>>
>
>


Reijo Pitkanen Posted on 2009-11-14 13:39:19.0Z
Date: Sat, 14 Nov 2009 15:39:19 +0200
From: Reijo Pitkanen <reijo.pitkanen@somermatic.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
Newsgroups: Advantage.FoxPro
Subject: Re: Free DBF-tables and triggers
References: <4afabd04@solutions.advantagedatabase.com> <4afb2ef8@solutions.advantagedatabase.com> <4afc25df@solutions.advantagedatabase.com> <4afc27bd@solutions.advantagedatabase.com> <4afcf25c@solutions.advantagedatabase.com> <4afd3e1d@solutions.advantagedatabase.com> <4afd971e@solutions.advantagedatabase.com> <4afdc0bb@solutions.advantagedatabase.com> <4afe942a@solutions.advantagedatabase.com>
In-Reply-To: <4afe942a@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 091114-0, 14.11.2009), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: 86.60.191.249
Message-ID: <4afeb2a6@solutions.advantagedatabase.com>
X-Trace: 14 Nov 2009 06:37:42 -0700, 86.60.191.249
Lines: 65
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!86.60.191.249
Xref: solutions.advantagedatabase.com Advantage.FoxPro:312
Article PK: 1109667

Further information:
It is the sp_AddTableToDatabase procedure that has the bug.
--
Reijo

Reijo Pitkanen wrote:
> When I add DBF-tables to dictionary with ARC, it accepts the table, but
> when you try to open it you get error messages:
>
> BrowseTable: Error 7041: File not found. Verify the specified path and
> file name is correct..
>
> When you look table properties with arc, the table name is correct
> uppercase, but the index file name has lowercase extension.
> For example according to ARC's table properties dialog the table
> ASIAKAS.DBF should have index file ASIAKAS.cdx.
> On Linux file system the index filename is ASIAKAS.CDX.
> I can open the table without any problems, if I rename the index file so
> that it has lowercase extension (ASIAKAS.cdx).
>
> Also the Query SELECT * FROM system.indexfiles gives all index filenames
> with lowercase extension.
> Conclusion: the "Add existing table(s)" function in ARC has a small bug,
> hasn't it?
> --
> Reijo
>
> Alex Wong (ADS) wrote:
>> Advantage does not assume the name is lower case, unless the
>> LOWERCASE_ALL_PATHS is true.
>>
>> The data dictionary preserve the case of the index file name at the
>> time the table and index were added to the data dictionary. If you
>> create the index in Advantage using ALL UPPER case, then there should
>> be no problem when the file is re-indexed by FoxPro. Make sure that
>> you do not set the LOWERCASE_ALL_PATHS to true when creating the index.
>>
>> You can see the index file names (with the preserved case) by
>> executing the following query in ARC - SELECT * FROM system.indexfiles.
>>
>> --
>> Alex
>>
>>
>>
>> "Reijo Pitkanen" <reijo.pitkanen@somermatic.com> wrote in message
>> news:4afd971e@solutions.advantagedatabase.com...
>>> I would rather keep Samba settings in their default values.
>>>
>>> Is it too difficult to preserve the case in filenames and/or give the
>>> user the ability to edit index file names in the dictionary?
>>>
>>> - Reijo
>>>
>>> Joachim Duerr (ADS) wrote:
>>>> Reijo Pitkanen wrote:
>>>>
>>>>> Yes Joachim, but this does not solve the problem because foxpro turns
>>>>> the file name to UPPERCASE when reindexing, and we are in the same
>>>>> situation where ADS does not find the index file.
>>>> for direct accessing the files on the linux box, you should set up
>>>> Samba to use lowercase only.
>>>>
>>
>>