I like to share my experience and I expect that somebody will tell me in this group: You are very stupid you could use this way ...
The task was to move tables from SQL to OE.
Steps:
- used CREATE table menu in MS SSMS
- run this with a SQL client (Squirrel) in OE (R)DMBS after only modifying timestamp/datetime type.
- in PDS I could see every new table -> done!
But I was wrong.
As I tried to use the second table of these new ones I got a ABL compile error, field or table does not exists.
That was strange, it was shown on the left table view and auto-complete proposal worked fine.
After 5 minutes testing I was just before calling PSC but then I remembered that Squirrel shows a DBO schema which I ignored as a load failure from my previous tests.
Checked again, this table was not in pub, it was in DBO.
O.k. - my fault but why PDS shows it??
Let's fix it, create table script by tool, drop table and delete DBO and run again to re-apply it to the OE (R)DMBS, now Squirrel shows it in pub, like others.
I am done!
No, what's this? PDS does not show the table like before, it's gone.
Restart DB, PDS -> The same effect.
Used DB Admintool, select this table and dump -> no df, it's empty like it has no fields, a zombie table, something new.
Why this table does not work as the other before? Something is different.
Compared create table script in Squirrel and identified a tinybit field definition (for logical)
After changing this to bit, drop and reload it seems to work as expected.
End of story
Brian,
I am aware of the different schema but why the table was visible in PDS as it was with tinybit field type in DBO and then invisible after I created it in the pub (default) schema?
After created in pub the table was visible in the admintool but I could not dump the structure.
That's mystic - I think.
In Squirrel I activated for my local db set schema 'pub' now as default with the session plugin.
It's working now, the developer was very nice and fixed it.
Stefan