Re: Access & OleDb - generating schema changes, problem with identity/counter fields.
From: Thomas Tomiczek [MVP] (t.tomiczek_at_thona-consulting.com)
Date: 11/05/04
- Next message: Jamie Collins: "Re: Should I use auto-number for my tables?"
- Previous message: Thomas Tomiczek [MVP]: "Re: I need to collate over a thousand photographs any ideas?"
- In reply to: Özden Irmak: "Re: Access & OleDb - generating schema changes, problem with identity/counter fields."
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 5 Nov 2004 11:32:29 +0100
Your tools have the tremenouds problem of:
* Being unable to work against an abstract schema.
* Being unable to work agaisnt other databases.
making them totally unsuitable for the task at hand.
The new database exists as schema (a graph of schema objects), and the tool
has to work against all databases we care for.
-- 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. "Özden Irmak" <ozdenirmak(at)isnet(dot)net(dot)tr> wrote in message news:eqTK8adwEHA.1308@TK2MSFTNGP09.phx.gbl... > Hi, > > Although the limitation for the Integer->AutoNumber still applies to them, > I would suggest our tools to compare and synchronize structure and data > changes in MSAccess : > > http://www.kliksoft.com/ > Klik! CompareLib and Klik! DataCompareLib > > Regards, > > Özden Irmak > Klik! Software > > "Thomas Tomiczek [MVP]" <t.tomiczek@thona-consulting.com> wrote in message > news:eZYMGTLwEHA.2732@TK2MSFTNGP12.phx.gbl... >> Hello, >> >> I am trying to auto sync db schemata (in access, among other databases). >> Means, there is a C# application that generates SQL for generating schema >> changes in the access database. >> >> I am stuck with two problems: >> >> ONE: how can I turn an int field into a counter/identity field? The >> following DDL statement: >> >> ALTER TABLE [ShpCountry] >> ALTER COLUMN [OID] COUNTER CONSTRAINT PK_OID PRIMARY KEY >> >> Produces the following error: OleDbException, Invalid field data type. >> (SQL State 3259). >> >> It does work creating a field of this type. adly we DO have some >> databases out where counter-fields were (erronously) generated as numeric >> fields, so I need to get this changes. >> >> TWO: how do I allow writing manual values into a counter field in SQL? We >> need to load "start data" into the database. I WOULD be ok with turning >> them back into a non-counter-field (i.e. numeric) to load the data, but >> then we end up again on problem ONE - turning them back INTO a counter. >> >> Anyone an idea how to handle this? I have all other stuff under control >> (index creation, drops, everything), just the "numeric to counter" gets >> on my nerves for weeks now. >> >> -- >> 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. >> >> >> > >
- Next message: Jamie Collins: "Re: Should I use auto-number for my tables?"
- Previous message: Thomas Tomiczek [MVP]: "Re: I need to collate over a thousand photographs any ideas?"
- In reply to: Özden Irmak: "Re: Access & OleDb - generating schema changes, problem with identity/counter fields."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
