Bug in DDT?


Author
Message
Howard Bennett
Howard Bennett
StrataFrame Novice (83 reputation)StrataFrame Novice (83 reputation)StrataFrame Novice (83 reputation)StrataFrame Novice (83 reputation)StrataFrame Novice (83 reputation)StrataFrame Novice (83 reputation)StrataFrame Novice (83 reputation)StrataFrame Novice (83 reputation)StrataFrame Novice (83 reputation)
Group: Forum Members
Posts: 57, Visits: 496
Not a big deal - but - I was changing some of the table structures after importing from a DBC. I started with the Primary Key - got to the Default Value - is was greyed out but ellipsis button was enabled - so I clicked on that and was able to enter a value from the list of options shown. Of course, it wouldn't save and wouldn't let me delete that out.



Thought you'd want to take a look and see if it's something you need to fix.



HB
Reply
Charles R Hankey
Charles R Hankey
StrataFrame VIP (1.3K reputation)StrataFrame VIP (1.3K reputation)StrataFrame VIP (1.3K reputation)StrataFrame VIP (1.3K reputation)StrataFrame VIP (1.3K reputation)StrataFrame VIP (1.3K reputation)StrataFrame VIP (1.3K reputation)StrataFrame VIP (1.3K reputation)StrataFrame VIP (1.3K reputation)
Group: Forum Members
Posts: 524, Visits: 30K
Test that early on in the process. I've found the one thing the DDT can be pretty unforgiving about is changing anything related to a PK (especially if you have it set to automatically create the PK index when you are in the table designer in DDT ) if you have an integer field, called it the pk but allow it to be updated, it may not let you change that later to auto increment. ( though maybe if you set the seed number right it won't be a problem. )



Anyway, easy enough to test on a couple of records just to be sure.



GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search