Issue 21864 - Problem with read/write access to mdb files
Summary: Problem with read/write access to mdb files
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC5
Hardware: PC Windows XP
: P4 Trivial (vote)
Target Milestone: ---
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-29 15:06 UTC by Unknown
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-10-29 15:06:04 UTC
Similar to my recent finding of a bug preventing read/write without using an 
index file in dBase files, here I have discovered that even with an index 
file, this is still a read-only connection. I attempted to add an Index on the 
Edit Tables dialog within the Data Sources dialog. Admittedly I had a relation 
between three tables in the first experiment. No dice. I had a double field in 
each table named ID that had a one-to-one relation. Not quite sure how to do 
one-to-many or many-to-many yet in OOo. That didn't work. I created another 
new connection & tried it with an index & another without. Is this implemented 
for read/write connectivity, yet? This would certainly be seen as crucial to 
those other office users that want to make a switch. Please fix this as it is 
the equivilent of being able to connect to Excel or Word.
Comment 1 marc.neumann 2003-10-31 10:56:28 UTC
Hi,

I don't get you.
PLease provide a steü-by-step description what your problem is and how
I can reproduce this. May be you can attach the mdb file with make the
problem.

Thanks & Bye 
Marc
Comment 2 Unknown 2003-10-31 15:13:43 UTC
Step-By-Step, here is what I did. I selected Data Sources from the 
Tools menu. In the Data Sources dialog, I selected New Data Source 
button. From there, I chose a Database type in the drop down combo 
box of ADO. I added a URL of PROVIDER=Microsoft.Jet.OLEDB.4.0;Data 
Source=C:\My Documents\HelloWorld.mdb which is the URL of my Access 
database. I named it ADO1. I went to the second tab for ADO, & 
essentially left the URL intact, used no User name, as a passcode is 
not required & I left the Password required checkbox blank. I chose 
to also leave the Use SQL92 naming constraints checkbox blank as I 
didn't want to get fancy. I just wanted a meat & potatoes, simple 
connection, with read & write capability. So, then, I moved to the 
Tables tab. I had several tables including all the MySys system 
tables, that Access auto-generates, & two of my own tables, with one 
query that I did in Access, called Query1. One is HelloPerson, & the 
other is HelloWorld. These are just a couple of tables that are not 
joined outside of OpenOffice. I chose to create a small experiment 
to see if I could get a read/write connection in ADO, after my 
recent discovery of a bug in the dBase driver such that it is being 
looked into in Issues 21685 & 21859 respectively. Please have a look 
at those issues, as well. Then, I selected the HelloPerson table. 
After selecting the HelloPerson Table, I then clicked on the Edit 
Table button, over top of the tables on the Data Source 
Administration dialog. I was informed by a message box that I had to 
save changes to the current operation, & I selected Yes, from the 
Yes/No options. Up poped the dialog for Table Design::HelloPerson. 
The table consists of two fields. ID which is a Double[Double], & 
Who which is Text[LongText]. Entry was left not required, & Length 
was left at 15 for ID, which had no Default value, or Format 
example. Actually I saw that the Who field had a range of 0 
characters, so I tried to edit that, & couldn't. I added one new 
field of Person2 & initially the Length showed as 536810910, which 
changed to 0, after I left the field. I added an Address field, & 
changed it to Text[VarChar]  & managed to get a 255 bit length. I 
now assume that the other two fields were the equivilent of memo 
fields. I clicked on the Index button, from the button bar up top. 
It told me to save my changes before I dealt with indexs & I did. I 
created an index of ID & made it unique. Then I saved the changes & 
came back to the previous dialog. I then pressed the button to save 
my changes there, just in case. I saved this as Table1. A dialog 
came up that informed me that I need a unique primary key & that I 
could only enter data if I set one. I chose to confirm that 
OpenOffice, should create one. It did as ID1. I closed the Table 
Design dialog. I then closed the Data Source Administration dialog, 
by pressing the OK button. Through the AutoPilot button, I created a 
new Form & up poped the First AutoPilot button of Choose Database. I 
chose my ADO1 Connection, with the Table or queries selected being 
the now well documented Table1. I pressed the button to select all 
fields, into the Fields in form box. I pressed Next. I selected the 
High Tech background, & the Columnar - Labels left box. I chose 3D 
look, with an Align left under table placement. The background image 
was tiled. I clicked on the Create button. I saved the form as 
Form_ADO1.sxw. I chose to leave the Save with password checkbox 
unchecked. There was no need to complicate this with additional 
security issues. First I had to see if this could work, in the first 
place, in read/write mode. From there I entered some data, as there 
was none in the table I formerly couldn't enter into & now it 
appears that I can. Ergo, it seems that the critical step, which was 
non-oblivious & counter-intuitive was that I had to get to the point 
where OpenOffice would create the primary key. Not sure what I did 
to get the primary key creation mechanism to click in. But, it 
appears that this resolves this.
Comment 3 hans_werner67 2004-02-02 12:26:10 UTC
change subcomponent to 'none'
Comment 4 marc.neumann 2004-04-05 16:18:50 UTC
close