Issue 55968 - Initial AutoValue of Primary Key differs depending upon creation method
Summary: Initial AutoValue of Primary Key differs depending upon creation method
Status: UNCONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO 2.0 Beta2
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-14 04:37 UTC by dlanderson
Modified: 2013-02-07 22:33 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description dlanderson 2005-10-14 04:37:05 UTC
OOo 2.0 RC2 - Base:
1) Use Wizard to create a table (e.g., Catagory: Business, Assets) and use Set
primary key to Use and existing fileld as primary key (e.g., Fieldname: AssetID
with Auto value)
2) Open Assets table, add a record, and notice that AssetID for first record is
equal to '0'
3) Close Assets table and copy it by selecting Assets object in Tables pane and
dropping it on Tables icon in Databse pane
4) Set Table name (e.g.,  Assets2) and Primary key and Name (e.g., ID)
5) Apply columns except AssetID, to prevent error due to creating of second
primary key, and create table
6) Edit Assets2 table, select ID field name, which is Primary Key, and set
AutoValue to "yes". 
7) Open Assets table, add a record, and notice that AssetID for first record is
equal to '1'
Note: This is a problem when importing tables with foreign keys: don't know when
to set foreign key values starting at '0' or '1'
Comment 1 christoph.lukasiak 2005-11-08 16:48:28 UTC
send further to: requirements