Open Office 2.0 import to dBase from text & spreadsheets

[Java script Dude]

For those who are missing the feature on how to import into Open Office
dBase app from text files and spreadsheets in OOO Base 2.0:

A wizard exists to import from spreadsheets only at this time but there
is no menu pick for `importing` at this time.

OOO 2.0 dBase Import SOP:
1) Open the spreadsheet -or- text file as a spreadsheet
2) Select range on spreadsheet you wish to import including title rows
if applicable
3) Open OOO dBase app
4) Drag selected range in spreadsheet over to `Tables` icon under
Database section -or- If Table is selected, you can also drag`n`drop
over into Tables section.

Once you drag in range, you will get an import wizard and the rest is
pretty intuitive.

Hopefuly they will make this process a little more intuitive in the
future.

T

[ ooo+moz+osx==:) ]

[Larry Linson]

"Java script Dude" wrote

For those who are missing the feature
on how to import into Open Office
dBase app from text files and spread-
sheets in OOO Base 2.0:

I am sure this is very useful to someone, but I wish it was more intuitive
to me why you posted this in a newsgroup clearly devoted to Microsoft
Access, when it has nothing to do with Access. <SIGH>

[David W. Fenton]

"Larry Linson" <bo*****@localhost.not> wrote in
news:qwCye.7270$kh3.7131@trnddc03:

"Java script Dude" wrote

For those who are missing the feature
on how to import into Open Office
dBase app from text files and spread-
sheets in OOO Base 2.0:

I am sure this is very useful to someone, but I wish it was more
intuitive to me why you posted this in a newsgroup clearly devoted
to Microsoft Access, when it has nothing to do with Access. <SIGH>

Inept advertising?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Java script Dude]

Being an ex-access developer, I now try to use Open Office as much as
possible. Having posts here will help other forward thinking people be
able to hack around Open Office as well and move away from Access.

The more Access developers start playing now with OOO Base, the sooner
it will get better!

The future is open ... get with the program!

[David W. Fenton]

"Java script Dude" <de********@yahoo.ca> wrote in
news:11**********************@o13g2000cwo.googlegr oups.com:

Being an ex-access developer, I now try to use Open Office as much
as possible. Having posts here will help other forward thinking
people be able to hack around Open Office as well and move away
from Access.

The more Access developers start playing now with OOO Base, the
sooner it will get better!

The future is open ... get with the program!

So, I was right -- you are doing marketing.

While discussions of the merits of programs in the same class as
Access are, I believe, valid contributions to the newsgroup, your
post was not. It wasn't a comparative post at all -- it wouldn't
help anyone learn anything at all about how the program differs from
or is similar to Access.

I have played with it in various incarnations of Open Office, and
was always distinctly underwhelmed. It always seemed like the people
writing the db module didn't quite understand the program they were
copying (Access), as well as made very poor choices on which things
the suite as a whole copied from Windows.

But I haven't looked at it in a long time. Has it vastly improved?
Is it now a useful tool for non-technical users? Is it now a usable
development platform? Neither of those were the case the last time I
looked at it.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Java script Dude]

I agree, my post was part marketting.

With that said, OOo has improved dramatically since the start of the
2.0 line which is still under development. There are many significant
improvements to the UI and functionality that make it a serious
contender in the future.

With the addition of the DataBase app, MicroSoft will better dig their
heels and start putting in some real patches into Office else loose
customers.

Being a programmer, I personally love the fact that OOo has a unified
object model where Office is highly abstracted. With a unified object
model, code that was written for vba in the spreadsheet app is 100%
compatible with code written in the database app and so on. This will
allow for developers to write some really sweet apps on top of OOo.

One last point is the lack of bloat in OOo. Installed OOo is about
190mb where I have seen MSO at nearly double that. (Actually my
sysadmin sent me a laptop where MSO took up over a gig ;P )

Personally, I still use Excel for some work becuase of some lingering
bugs in OOo but hopefully I will fully migrate before the end of the
year once 2.0 becomes stable.