Re: Access & OleDb - generating schema changes, problem with identity/counter fields.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Thomas Tomiczek [MVP] (t.tomiczek_at_thona-consulting.com)
Date: 11/05/04 

Date: Fri, 5 Nov 2004 11:31:01 +0100

"david epsom dot com dot au" <david@epsomdotcomdotau> wrote in message
news:%23JM0X$gwEHA.3824@TK2MSFTNGP15.phx.gbl...
>> How do I do this without the possibility to RENAME a table?
>
> Two options: use DAO to rename the table, or create
> a view using the old table name after deleting the
> old table. (renaming a table breaks relationships)

I will live with two copies for now.

>> seriously (!) sucks. If the table is non-trivial, this is a
>> significant amount of work for the database and blows up the
>
> If the table has a lot of relationships to other
> tables, it is not trivial. A make table query
> won't re-create the relationships.

Total non-issue as the code to tear down and recreate the relationships is
already there. It WAS trivial, thanks to the manipulation framework already
in place. Both methods are less than one screen full of text.

> I -personally- would not use autonumber fields where anything
> like this is contemplated. My belief is that numeric indexes
> will always bite you sooner or later: sooner, if you have to
> build your own index generator; later, if you have to deal with
> autonumber fields. So--- I use autonumber fields if the upfront
> saving is greater than the risk of later problems. I use code
> number generators if the risk of later problems is greater than
> the upfront savings.

Personally I do not care what you - or I - personally would like to do. This
is for a tool that allows this use, too, and so it just HAS TO WORK. If some
dude outside wants counter-fields, he gets counter-fields, and I am not the
person to stop him from doing so.

I fully agree in terms of "it is wise", but - it is not my decision. We
provide developer tools. 

-- 
Regards
Thomas Tomiczek
THONA Software & Consulting Ltd.
(Microsoft MVP C#/.NET)
(CTO PowerNodes Ltd.)
---
Still waiting for ObjectSpaces? Try the EntityBroker today - more versatile, 
more powerfull.
And something in use NOW. for the projects you have to deliver - NOW.