When I try to append a Text File to a table .. it works bad .. please tell
me experiences !!



Thanks

Hi Pedro

Pedro Hernández wrote:
> When I try to append a Text File to a table .. it works bad .. please tell
> me experiences !!

You don't say how you are appending the text to the database (I presume 
that was what you really meant to say instead of table...).

But, one thing that has been mentioned in the past is the fact that 
there is a replacement for the 'append from...' functionality in Xbase++ 
that can be downloaded from the ACSN section of the Alaska website.

If that doesn't help, it may be worth giving more info about what you 
are doing...

Regan

Regan,

>> When I try to append a Text File to a table .. it works bad .. please tell
>> me experiences !!
> 
> You don't say how you are appending the text to the database (I presume 
> that was what you really meant to say instead of table...).

In the xBase world, we use the terms 'table' and 'database'
interchangeably.  However in most other IT realms, a table is a collection
of data, and a database is a collection of tables.

If you use 3rd level normalisation (most people do), then an invoicing
system might have one table for the customer details, another table for
invoices, and another table for individual items that can be purchased,
with the invoices table using keys to locate the records in the other
tables.

In relational database terms, the customer table and the items table are
complete, in that they do not rely on other tables.  hese can be considered
a database in their own right.  The invoices table though is meaningless
(or at least informationally challenged ) without the other two, and so
is only part of a database.  Generally, all three tables are collected
together into a single database because they are related items.

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

SysOp's law #1 - New users always find the glitch.

Hi Phil

Phil Ide wrote:
> Regan,
> 
> 
>>>When I try to append a Text File to a table .. it works bad .. please tell
>>>me experiences !!
>>
>>You don't say how you are appending the text to the database (I presume 
>>that was what you really meant to say instead of table...).
> 
> 
> In the xBase world, we use the terms 'table' and 'database'
> interchangeably.  However in most other IT realms, a table is a collection
> of data, and a database is a collection of tables.
> 
> If you use 3rd level normalisation (most people do), then an invoicing
> system might have one table for the customer details, another table for
> invoices, and another table for individual items that can be purchased,
> with the invoices table using keys to locate the records in the other
> tables.
> 
> In relational database terms, the customer table and the items table are
> complete, in that they do not rely on other tables.  hese can be considered
> a database in their own right.  The invoices table though is meaningless
> (or at least informationally challenged ) without the other two, and so
> is only part of a database.  Generally, all three tables are collected
> together into a single database because they are related items.

Point taken!

Regan

Hi Phil,

No offense but (IMO) that reply was a little pedantic -- 
e.g. "If you use 3rd level normalisation (most people
do)" --  ... but you are right, of course.

Robert

Robert,

> No offense but (IMO) that reply was a little pedantic --
> e.g. "If you use 3rd level normalisation (most people
> do)" --  ... but you are right, of course.

I don't think that Phil was pedantic.

The problem is that IT terms are ambiguous.

That's what I had to deal with all the time when writing the Xbase++
docs.

Tell me what these terms mean 

  database
  object
  table

BTW, one reason for the quality of the Xbase++ docs is that these terms
are used only in the very same context. They are not ambiguous in the
Xbase++ docs.

Regards,

Hannes

Robert,

> No offense but (IMO) that reply was a little pedantic -- 
> e.g. "If you use 3rd level normalisation (most people
> do)" --  ... but you are right, of course.

I try not to, but sometimes it might come across that way.  I generally use
3rd level normalisation, but sometimes use 4th or even 5th level.  I only
once went all the way to 7th level and still have nightmares about it.

When I said "If you use 3rd level normalisation...", I didn't mean "You DO
use 3rd level, don't you?".  I meant it more as a predicate to the example
of a database being broken into several tables.

My humblest apologies if anyone took offence, and thanks Robert for keeping
me in line 

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

Tagline thievery... on the next Geraldo!

Hi Hannes and Phil,

To Phil,
> and thanks Robert for keeping me in line 

I certainly cannot do that or would not even dare to try
.

To Hannes,
>Tell me what these terms mean 
  database
  object
  table

Well, here is my try at definitions:
1) database:  A collection of fields organized by records.
2) object:  An abstract progamming entity containing methods
and properties.
3) table: A representation of database cells by row and
column.

But that is just a guess..

Robert

Robert,

> >Tell me what these terms mean 
>   database
>   object
>   table
> 
> Well, here is my try at definitions:
> 1) database:  A collection of fields organized by records.
> 2) object:  An abstract progamming entity containing methods
> and properties.
> 3) table: A representation of database cells by row and
> column.
> 
> But that is just a guess..

That's not bad as definition 

Hannes

Robert,

>>Tell me what these terms mean 
>   database
>   object
>   table
> 
> Well, here is my try at definitions:
> 1) database:  A collection of fields organized by records.
> 2) object:  An abstract progamming entity containing methods
> and properties.
> 3) table: A representation of database cells by row and
> column.
> 
> But that is just a guess..

Looks good, but (isn't there always one of these?), if you go to 6th or 7th
level normalisation:

database = object = entity
table = object = entity
object = entity
field = object = entity

Taking this to extremes:

A database is equivalent to a table or a field, and an object can be a
field, a computation, a table, a record or a database (or any combination
of these or a combination of subsets of these).

In fact, at 6/7N, you don't deal with data at all, but only abstract
concepts of data.  In theory, this is the way SQL engines work (in practice
they can do what the hell they like).

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

If you believe THAT, I have a BRIDGE for sale...

Hello Pedro Hernndez

De donde eres ?

Saludos
Osvaldo Ramirez