andrew wrote:
Hi Barbara,
I wasn't gong to send another email on this thread again tonight -
but.since this one just arrived.
I read over your earlier message, with the numbered issues a couple of
times, and had a few more comments. Mostly dealing with some of the
features for data exchange between Base / Writer and Calc that perhaps
you are not familiar with yet.
I'm all ears!
Also, with some ideas about setting up this type of distributed data
entry system, with a centralized roll up database, you are describing.
I've had a little experience with that type of thing in the past, as
it sounds like you have also. I would be interested in why you are
considering using Writer or Calc files for the data entry and not
separate Base files.
Three reasons, mainly. One, just about everybody has and is comfortable
with a word processor, many have and pretty much understand a
spreadsheet, but very few have a database, never mind understand it. I'm
converting everybody I can to OOo so Base becomes available, but it
hasn't happened yet and I'm dealing with some folks with very basic
skill sets and an aversion to learning new stuff. (And all of us are
doing this on a volunteer basis.) Two, I don't think my data lends
itself well to being broken apart much finer than it is now. If you'd
like, I can send you (off-list) a more complete description of what I
have and the processes involved. Three, the editing capabilities within
Base are pretty restrictive. Writer is best, Calc second-best (I really
need text wrap, for instance - maybe it's there and I haven't seen it?
I've spent most of my time in Writer), Base a poor third.
I am not really sure if the dev mailing list is the correct place for
that discussion. Perhaps the users list or the user forum would make
more sense, it would be up to you.
For now though it is getting late here, so that will wait till the
morrow. ( or I should say - later today )
Barbara Duprey wrote:
andrew wrote:
Barbara Duprey wrote:
(Comments in message)
Yes, that was the specific question (let's call it Issue 1). In
this case, it would be complicated by the fact that Base did not
define the PK it generated for the original .dbf import as
auto-increment.
This one has a work around.
If you drag and drop onto Base, then when the copy table wizard
opens, instead of defining the table and copying the data in, in one
step you simply create the table structure. Then when the field type
INTEGER or BIGINT is marked as the PK it is created as AUTO_INCREMENT.
After this drag and drop again, but this time only append the data
to an existing table - then the data comes in, either include the PK
value from the old table - this works as long as the values are
unique, or simply leave that field out and new keys are made. This
later approach has a down side if there are FK relationships in your
schema of course.
Yes, if I'd known how Base would handle it that's what I'd have done,
but I didn't. The redefinition process is doable, but cumbersome.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
