ODBC on NativeDB over 4 gigs

Hi @ll!

Ich have a question regarding the "old" ODBC driver for Native 3.1.
The driver Version is 55.00.13

We have a customer whose Native Database Size has exceeded the 4 Gig limit 
and therefore we have split the Database into 5 parts.
XAL itself is running fine, unfortunatly the ODBC crashes when he tries to 
read data into Excel.
The symptom is, that after calling the "new query" entry from the
excel menu 
and clicken through the Query assistant, after choosing "return data to 
excel", just nothing more happens.
Usually you get a dialog where you can choose in which cell of the 
spreadsheet the returned data shall start.
The effect can be reproduced on all machines and even on our inhouse 
installation of the system.

We have testet this on a slightly older database of this customer taht was 
still below the 4 gig limit. After splitting this database into 5 parts and 
the ODBC worked fine on that.

Is there a known limitation to the ODBC driver not working with Native 
databases over 4 gigs? Or do we have to search for another cause for this 
behaviour?

To add to the misery, the customer is already in the process of switching to 
XAL 3.5 with MS-SQL, and its just a question of weeks until the new system 
will  become productive. But until then they depend on the ODBC connection, 
to get data into their Excel Spreadsheets.

I hope somebody has at least a hint on this.

Stefan

Hello Stefan,

The ODBC driver does not support running against split-file Native 
databases.

In more recent versions of the ODBC driver it is stated in the ODBC help 
file:
Known Issues
  a.. The ODBC driver for Microsoft® Dynamics C5 or for Microsoft® XAL does 
not support ODBC connection to split-file databases.

-- 
Best Regards
Henrik Hansen [MSFT]
Tecnical Program Manager Microsoft Dynamics C5 & Microsoft XAL
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

"Stefan Wunschel" <Stefanotti@msn.com> wrote in message 
news:%23HxDUTGKIHA.2064@TK2MSFTNGP06.phx.gbl...
> Hi @ll!
>
> Ich have a question regarding the "old" ODBC driver for Native
3.1.
> The driver Version is 55.00.13
>
> We have a customer whose Native Database Size has exceeded the 4 Gig limit

> and therefore we have split the Database into 5 parts.
> XAL itself is running fine, unfortunatly the ODBC crashes when he tries to

> read data into Excel.
> The symptom is, that after calling the "new query" entry from the
excel 
> menu and clicken through the Query assistant, after choosing "return
data 
> to excel", just nothing more happens.
> Usually you get a dialog where you can choose in which cell of the 
> spreadsheet the returned data shall start.
> The effect can be reproduced on all machines and even on our inhouse 
> installation of the system.
>
> We have testet this on a slightly older database of this customer taht was

> still below the 4 gig limit. After splitting this database into 5 parts 
> and the ODBC worked fine on that.
>
> Is there a known limitation to the ODBC driver not working with Native 
> databases over 4 gigs? Or do we have to search for another cause for this 
> behaviour?
>
> To add to the misery, the customer is already in the process of switching 
> to XAL 3.5 with MS-SQL, and its just a question of weeks until the new 
> system will  become productive. But until then they depend on the ODBC 
> connection, to get data into their Excel Spreadsheets.
>
> I hope somebody has at least a hint on this.
>
> Stefan
>
> 

Hello Henrik!

Thanks for the quick answer.
Fortunatly the ODBC is much better then the manual thinks.
You can run the 3.10.011 for XAL 3.10 SP3 - ODBC Driver version 5.50.0.13
against split files.
As we found out the problem ist located in the split definition:

Since the customer uses different drive letter Mappings on different 
machines, we made the
Splitfile entry using relative paths like this:

.\ 0 1000 50
.\ 1 1000 50

After changing this back to literal paths everything worls fine:

X:\V310\XAl 0 1000 50
X:\V310\XAl 1 1000 50

Regards
 Stefan Wunschel


"Henrik Hansen [MSFT]" <hhanse@online.microsoft.com> schrieb im
Newsbeitrag 
news:F35BF938-E341-42E2-A71B-5D4D4D713DAE@microsoft.com...
> Hello Stefan,
>
> The ODBC driver does not support running against split-file Native 
> databases.
>
> In more recent versions of the ODBC driver it is stated in the ODBC help 
> file:
> Known Issues
>  a.. The ODBC driver for Microsoft® Dynamics C5 or for Microsoft® XAL does

> not support ODBC connection to split-file databases.
>
> -- 
> Best Regards
> Henrik Hansen [MSFT]
> Tecnical Program Manager Microsoft Dynamics C5 & Microsoft XAL
> =====================================================
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers
no 
> rights.
>
> "Stefan Wunschel" <Stefanotti@msn.com> wrote in message 
> news:%23HxDUTGKIHA.2064@TK2MSFTNGP06.phx.gbl...
>> Hi @ll!
>>
>> Ich have a question regarding the "old" ODBC driver for
Native 3.1.
>> The driver Version is 55.00.13
>>
>> We have a customer whose Native Database Size has exceeded the 4 Gig 
>> limit and therefore we have split the Database into 5 parts.
>> XAL itself is running fine, unfortunatly the ODBC crashes when he tries

>> to read data into Excel.
>> The symptom is, that after calling the "new query" entry from
the excel 
>> menu and clicken through the Query assistant, after choosing
"return data 
>> to excel", just nothing more happens.
>> Usually you get a dialog where you can choose in which cell of the 
>> spreadsheet the returned data shall start.
>> The effect can be reproduced on all machines and even on our inhouse 
>> installation of the system.
>>
>> We have testet this on a slightly older database of this customer taht

>> was still below the 4 gig limit. After splitting this database into 5 
>> parts and the ODBC worked fine on that.
>>
>> Is there a known limitation to the ODBC driver not working with Native

>> databases over 4 gigs? Or do we have to search for another cause for
this 
>> behaviour?
>>
>> To add to the misery, the customer is already in the process of
switching 
>> to XAL 3.5 with MS-SQL, and its just a question of weeks until the new

>> system will  become productive. But until then they depend on the ODBC

>> connection, to get data into their Excel Spreadsheets.
>>
>> I hope somebody has at least a hint on this.
>>
>> Stefan
>>
>>
>