#1  
Old 27th September 2003, 02:45 PM
Pierre Demers
 
Posts: n/a
Default Restructuring tables...

Hello,

I don't use Nexus but I am planning to give it a good try in the next few
months, probably november(just in time to pay full price . I was wondering
what you guys use for restructuring tables?

With the dbms that I use at the moment(Advantage), there is a free component
made public by Mr. Peter Mora that does the restructuring task very easy.
Mr. Mora is a gentlemen. I have communicate with him a few times and he is
very cooperative. Peter is now using DBISAM and has made public again his
restructuring component called TDBISAMDesignTable.

I am quite positive that Mr. Mora would be willing to grant the permission
to adapt his component for the Nexus community. If someone has some spare
time and is willing to do the job. Drop me a line and I'll ask Mr. Mora if
he agrees to it.

Pierre


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.521 / Virus Database: 319 - Release Date: 2003-09-23


  #2  
Old 27th September 2003, 06:43 PM
Roberto Nicchi
 
Posts: n/a
Default Re: Restructuring tables...

"Pierre Demers" <dempier@videotron.ca> wrote in news:3f74f9ff@wic040d.:

> Hello,
>
> I don't use Nexus but I am planning to give it a good try in the next
> few months, probably november(just in time to pay full price . I was
> wondering what you guys use for restructuring tables?
>


What do you meen exactly with Restructuring ? Reparing ? Change the table
structure ? What exactly this component do ?

thank you

Roberto
  #3  
Old 28th September 2003, 12:16 AM
Pierre Demers
 
Posts: n/a
Default Re: Restructuring tables...

Hello Roberto,

> What do you meen exactly with Restructuring ? Reparing ? Change the table
> structure ? What exactly this component do ?


Here is a bit of Peter description :

<Extra Properties:
DsnFieldDefs -- Field definitions
DsnIndexDefs -- Index definitions

Extra Methods:
CompareStructure -- Does the stored structure match the existing DAT
file?
ExtractStructure -- Extract and store structure from an existing DAT
file.
CreateTable -- Create DAT, IDX, BLB files based on stored
structure.
IndexTable -- Create/overwrite IDX file on existing table.
UpdateTable -- Restructures the data file.
PrintStructure -- Print the stored structure to a text file.

It's main functions:

1. Determines if a valid table, index, and memo file exists on the
drive. This can occur either at design time by right-clicking on
the component and choosing "Table Exists" from the pop-up menu,
or at runtime by calling "TableExists" method. Returns true if
successful.

2. Extracts the table, index, and memo structure of a valid DAT table.
This can occur either at design time by right-clicking on the
component and choosing "Extract Structure" from the pop-up menu,
or at runtime by calling "ExtractStructure" method.

3. Enables programmer to add/edit/delete field and index definitions
at design time using the object inspector.

4. Compares the stored structure with the structure of the DAT files
on the drive. This can be at design time by right-clicking on the
component and choosing "Compare Structure" from the pop-up menu,
or at runtime by calling "CompareStructure" method. At runtime,
it returns true if the structures are the same. At designtime,
it displays a message dialog as to whether the structures match.

5. Creates DAT table, index, and memo files using stored structure.
This can be at design time by right-clicking on the component and
choosing "Create Table" from the pop-up menu, or at runtime by
calling "CreateTable" method.

6. Updates the DAT table, index, and memo files on the drive by
restructuring them with the stored structure. This can be at
design time by right-clicking on the component and choosing
"Update Table" from the pop-up menu, or at runtime by calling
"UpdateTable" method.

7. Prints the DAT table and index structure to a text file that can
be viewed by any ASCII editor (ex: NOTEPAD.EXE). This can be at
design time by right-clicking on the component and choosing
"Print Structure" from the pop-up menu, or at runtime by calling
"PrintStructure" method.


When I deploy my applications, I do not include the DAT table, index,
and memo files. I only send the EXE. When the app starts, it checks
to see if the tables already exist on the drive. If not, they are
created from the TDBISAMDesignTables.

When the app starts, if it finds the DAT table, index and memo files,
then it compares the structure with the stored structure in the
TDBISAMDesignTable. If the structures do not match, then the tables are
restructured based on the stored structure in the TDBISAMDesignTable.

It handles fieldnames that change, such as "PHONE" to "HOME_PHONE".
It also handles fieldtype change, such as ftInteger to ftString.>

--------------------

You can use this wonderful component in many ways. For my app., I made a
utility program that takes care of restructuring fields (add fields, modify
fields and even move the fields) on a major update. Works like a charm and I
have been using it for more than 2 years.

There are many ways you can use it. You can also use it to create your
tables. It's not a source maker like what you have done( I think), but it's
a component that stores the info for a specific table and with those infos,
you can do many things. Print, Create, Add, Mofidy, etc. Simply great from
my point of vue. I would have to re-think my whole update process without
it. ;(

HTH
Pierre




---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.521 / Virus Database: 319 - Release Date: 2003-09-23




  #4  
Old 28th September 2003, 02:37 AM
Alessandro Romano
 
Posts: n/a
Default Re: Restructuring tables...

Hi,

I have modified the version of NxSourceMaker 1.08 to do this.
the change works in this way:
1) if the table doesn't exist--> it is created.

2) if the table Exists then it is compared with the dictionary of the
table on the disk.
if the dictionaries are different a restructuring of table is performed
on the disk.

the limit is on it renames some fields. this is not managed.

PS: in this period I am very busy... and I have had little time
to work on it (the code must be optimized...!).

uploaded in binaries...

sorry for the English : -)

Alessandro Romano
staff@arlsoft.it
www.arlsoft.it
www.windress.it

"Pierre Demers" <dempier@videotron.ca> ha scritto nel messaggio
news:3f757fad@wic040d....
> Hello Roberto,
>
> > What do you meen exactly with Restructuring ? Reparing ? Change the

table
> > structure ? What exactly this component do ?

>
> Here is a bit of Peter description :
>
> <Extra Properties:
> DsnFieldDefs -- Field definitions
> DsnIndexDefs -- Index definitions
>
> Extra Methods:
> CompareStructure -- Does the stored structure match the existing DAT
> file?
> ExtractStructure -- Extract and store structure from an existing DAT
> file.
> CreateTable -- Create DAT, IDX, BLB files based on stored
> structure.
> IndexTable -- Create/overwrite IDX file on existing table.
> UpdateTable -- Restructures the data file.
> PrintStructure -- Print the stored structure to a text file.
>
> It's main functions:
>
> 1. Determines if a valid table, index, and memo file exists on the
> drive. This can occur either at design time by right-clicking on
> the component and choosing "Table Exists" from the pop-up menu,
> or at runtime by calling "TableExists" method. Returns true if
> successful.
>
> 2. Extracts the table, index, and memo structure of a valid DAT table.
> This can occur either at design time by right-clicking on the
> component and choosing "Extract Structure" from the pop-up menu,
> or at runtime by calling "ExtractStructure" method.
>
> 3. Enables programmer to add/edit/delete field and index definitions
> at design time using the object inspector.
>
> 4. Compares the stored structure with the structure of the DAT files
> on the drive. This can be at design time by right-clicking on the
> component and choosing "Compare Structure" from the pop-up menu,
> or at runtime by calling "CompareStructure" method. At runtime,
> it returns true if the structures are the same. At designtime,
> it displays a message dialog as to whether the structures match.
>
> 5. Creates DAT table, index, and memo files using stored structure.
> This can be at design time by right-clicking on the component and
> choosing "Create Table" from the pop-up menu, or at runtime by
> calling "CreateTable" method.
>
> 6. Updates the DAT table, index, and memo files on the drive by
> restructuring them with the stored structure. This can be at
> design time by right-clicking on the component and choosing
> "Update Table" from the pop-up menu, or at runtime by calling
> "UpdateTable" method.
>
> 7. Prints the DAT table and index structure to a text file that can
> be viewed by any ASCII editor (ex: NOTEPAD.EXE). This can be at
> design time by right-clicking on the component and choosing
> "Print Structure" from the pop-up menu, or at runtime by calling
> "PrintStructure" method.
>
>
> When I deploy my applications, I do not include the DAT table, index,
> and memo files. I only send the EXE. When the app starts, it checks
> to see if the tables already exist on the drive. If not, they are
> created from the TDBISAMDesignTables.
>
> When the app starts, if it finds the DAT table, index and memo files,
> then it compares the structure with the stored structure in the
> TDBISAMDesignTable. If the structures do not match, then the tables are
> restructured based on the stored structure in the TDBISAMDesignTable.
>
> It handles fieldnames that change, such as "PHONE" to "HOME_PHONE".
> It also handles fieldtype change, such as ftInteger to ftString.>
>
> --------------------
>
> You can use this wonderful component in many ways. For my app., I made a
> utility program that takes care of restructuring fields (add fields,

modify
> fields and even move the fields) on a major update. Works like a charm and

I
> have been using it for more than 2 years.
>
> There are many ways you can use it. You can also use it to create your
> tables. It's not a source maker like what you have done( I think), but

it's
> a component that stores the info for a specific table and with those

infos,
> you can do many things. Print, Create, Add, Mofidy, etc. Simply great from
> my point of vue. I would have to re-think my whole update process without
> it. ;(
>
> HTH
> Pierre
>
>
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.521 / Virus Database: 319 - Release Date: 2003-09-23
>
>
>
>



  #5  
Old 28th September 2003, 07:05 AM
Pierre Demers
 
Posts: n/a
Default Re: Restructuring tables...

Thanks guys, I will have a look. But out of curiosity, you could also check
Peter's component.

Pierre


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.521 / Virus Database: 319 - Release Date: 2003-09-23


  #6  
Old 29th September 2003, 12:46 AM
Bo Nielsen
 
Posts: n/a
Default Re: Restructuring tables...

Without knowing Peters component it sounds for me, that its more like what
the dictionary part already does in Nexus!
Bo Nielsen




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem with Adding a DSN in the ODBC Manage and encrypted tables Morgan Klebom nexusdb.public.support.odbc 3 13th June 2011 01:30 PM
Encrypted Data Tables? Shane Stump nexusdb.public.support.odbc 3 29th October 2008 03:26 PM
Password protected tables Vladimir Velichko nexusdb.public.support.adoprovider 3 2nd June 2008 09:39 PM
Encrypted Tables? Shane Stump nexusdb.public.support.odbc 2 11th December 2007 11:53 AM
ODBC driver and encrypted tables Oleav nexusdb.public.support.odbc 0 23rd April 2007 07:02 PM


All times are GMT +11. The time now is 08:26 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.