While trying to use the nice DBISQL Import/Export facility to import data from a different database (directly from that database, not via text file), I noticed that the assistant ignores tables owned by dbo.
In my dev database, all user tables are owned by "dbo", too (due to my (bad) MS SQL habits...), and the assistant lists no tables to import from. Unfortunately, I have not found any option to adapt that behaviour (say, like Sybase Central's "owner filter").
The export shows the same filtering: Tables owned by dbo are not listed as target tables.
Why is that?
(I managed to work around by taking the opposite direction, i.e. by exporting the dbo-owned tables into the source database which - somewhat luckiliy - uses a different schema so those tables are listed as desired.)
Note, I'm not able to use the export/import via text files as the tables contain BLOBs making a CSV-like format problematic...
I'm using 18.104.22.16803 here.
I'm aware that the particular "dbo" owner is less common in SQL Anywhere than in ASE/MS SQL, and I do understand that the according schema may be hidden by default when dealing with user tables, however IMHO there should be an option to treat "dbo" as first-citizen schemata here, too...