James,
Having considered the same option some time back I did some tests and once the 
DBC is opened then access to the tables in it is considerably quicker than free 
tables. Also the additional security offered by the DBC is useful. All in all I 
can't see any valid reason for not having the DBC present as long as you 
remember the "set validate" option to off in VFP 9.

Also the OLEDB and ODBC drivers work much quicker with the DBC's as I also did 
lots of tests using these.

One feature that you may not use but could investigate is the use of SP's and 
Triggers on the DBC which help to make the DBC more like Client Server and in 
fact you can write a Client server app to access either conventional DBC or 
MySQL, M$SQL with minimal change whereas converting free tables to work as 
Client/Server becomes more of a pain.

Maybe taking a second breath and thinking about the disadvantages of going back.
  
Just my 2c worth.
Dave


-----Original Message-----
From: ProFox [mailto:[email protected]] On Behalf Of James Harvey
Sent: 08 July 2013 14:03
To: 'ProFox Email List'
Subject: RE: Fee tables from DBC

Other than long fieldnames and primary keys I wasn't using any of the other 
features of a DBC, but did have occasional issues with the DBC, so to simplify 
things for my replacement I thought it would be best to "rollback"
the DBC.

It seems that primary keys are automatically converted to candidate keys when 
the table is removed from the dbc.

James E Harvey
M.I.S.
Hanover Shoe Farms, Inc.
www.hanoverpa.com
office: 717-637-8931
cell: 717-887-2565
fax: 717-637-6766


-----Original Message-----
From: ProFox [mailto:[email protected]] On Behalf Of Richard Kaye
Sent: Monday, July 08, 2013 8:58 AM
To: [email protected]
Subject: RE: Fee tables from DBC

Besides the long column names are you using any other DBC features? Primary
key tags? Default values?

One strategy might be to pull the data out of all DBC tables into free
tables using SQL or even COPY TO (just make sure you use the FREE clause if
you use COPY TO). The advantage to the latter is you could create the CDX at
the same time as the DBF. It's pretty easy to programmatically iterate
through all the tables in a DBC.

What's the motivating factor for dumping the DBC?

--
rk

-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of James
Harvey
Sent: Monday, July 08, 2013 8:43 AM
To: [email protected]
Subject: Fee tables from DBC 

I think I've finally decided to stop using a DBC, and would like to revert
back to a "Free" table scenario.

One issue is that there are about a dozen field names in several tables
longer than 10 char that will need to be changed in the structure and code.

After that I will open the DBC and then "remove" each table.

Once that's done I suppose I could just open Windows Explore and delete the
dbc from the folder?

A complete backup will be made prior to any changes being made.

Does anyone who has done this before have any advice?

TIA

Jim

James E Harvey
M.I.S.
Hanover Shoe Farms, Inc.
www.hanoverpa.com
office: 717-637-8931
cell: 717-887-2565
fax: 717-637-6766



[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to