Issue 59728 - dBase support is broken since 2.0.1
Summary: dBase support is broken since 2.0.1
Status: CLOSED DUPLICATE of issue 59361
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.1
Hardware: Other Windows 2000
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: dbaneedsconfirm
QA Contact: issues@dba
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2005-12-23 21:19 UTC by rene_leonhardt
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description rene_leonhardt 2005-12-23 21:19:58 UTC 
I am working in a small network with OOo clients and dBase .dbf files.

Since I upgraded to OOo 2.0.1 none of the existing .odb files with dBase
database connections are working anymore.
The connection test works but tables are not visible and not accessible.

I made a new .odb dbase connection in OOo 2.0.1 with the same result.

The I deinstalled 2.0.1, reinstalled 2.0.0 and the old and the new .odb files
are working without problems again.


Keep up the good work,
René
Comment 1 marc.neumann 2006-01-02 09:08:06 UTC 
Hi,

I can't reproduce this.

Can you tell me something more about your environment.
- the name of the dbase files 
- the path to the files

Bye Marc
Comment 2 rene_leonhardt 2006-01-02 21:17:11 UTC 
The names of the dBase files are: A-ARTIKE.DBF, A-HISTOR.DBF, A-KRITER.DBF,
A-RABATT.DBF, A-SBRIEF.DBF, ADRESSEN.DBF, ARTIKEL.DBF, AUF-HGR.DBF, F-POS.DBF,
F-RUECK.DBF, F-STAPOS.DBF, F-STATIS.DBF, FAKTU.DBF, FORMULAR.DBF, L-BESTEL.DBF,
L-KRITER.DBF, L-SERIE.DBF, L-STUECK.DBF, L-WG.DBF, L-ZUAB.DBF, S-BEMERK.DBF,
S-OPOSTE.DBF, S-STAMM.DBF, S-STAPEL.DBF, S-USER.DBF, S-VERKAU.DBF, SYBEX.DBF,
SYBEXA.DBF, SYBEXL.DBF

The path is D:\Sybex\Sybex\GMBH (local) or \\Windows2000\D\Sybex\Sybex\GMBH
(network).

Normally I use a connection with a network path to use the same .odb file from
all network clients, but the error occurs with a new .odb file with a local
path, too.
Comment 3 Frank Schönheit 2006-01-03 11:17:45 UTC 
known as issue 59361. Detecting upper-case extensions broke towards 2.0.1 :(

*** This issue has been marked as a duplicate of 59361 ***
Comment 4 Frank Schönheit 2006-01-03 11:19:49 UTC 
closing duplicate