Hi,
I know that the recommendation is not to use it anymore, especially in SQL.
As I'm dealing with an embedded and legacy base I come across, with the following scenario (also in df20):
The visual object is confusing, especially when selecting the fields:
The field size is being registered in a different way to what was used with the embedded.
That's fine by me, if this is what was expected since since the Dataflex x SQL migration, everything works fine.
Now I need to create a new base.
Using DBBuilder for the first time in DF20.1, I chose to create the embedded database (this seems to be a more dynamic way of building).
I started typing the fields and after selecting the first relationship the program aborted without issuing any error.
The filelist had been updated, but all data was lost.
Delete the filelist information and repeat the process.
I was saving the screen step by step, for evidence of the abortion, which did not happen.
So life goes on...
When I got to the point of creating another overlap relationship, I can't since the selection combo must be coming across, with the difference in the size of the overlap field, which in the embedded bank: 4 bytes instead of 18.
It was no use deselecting the object:
(*) I decided to delete the embedded base and create it in SQL, and the size of the overlap field occupies another position: 5 bytes.
I think, that something needs to be adjusted or is it time to abandon the overlap?
Regards,
Edgard Luis Paneque
(*) Modification, including testing of creation in SQL.