Most editing is perfomed in the Inspector, if the inspector isn't visible you need to use to make it visible.
This is most likely a limitation in the parser. There are lots of variants of SQL and there are things the parser doesn't support.
If you send a sample of the SQL that fails to us at support@malcolmhardie.com, we'll do our best to make the parser recognize it
First of all, sorry about this. Some names cause problems when passed between the payment processor and our own system.
If you email us at support@malcolmhardie.com we'll immediately issue a new serial number for you. We believe we've fixed this problem for future licenses.
We try not to make announcements about future plans, but if you send a request in to us at support@malcolmhardie.com we'll add it the feature request list.
Quite a lot of the features in SQLEditor are the result of features that were requested, plus the more requests that we get for particular things, the more likely they are to appear.
Unfortunately this is just the way that SQLEditor was written and it made sense to the developer (awh) at the time.
We're looking into whether this can be supported for a future release.
Sometimes new object types are added to SQLEditor, e.g. Views were added in v1.8, Check Constraints in v3.1. However earlier versions don't know how to deal with these features. Older versions will open and edit the document, but cannot read the newer objects. When saving the new objects are deleted. In order to prevent this you need to use a copy of the file or the newer objects will be lost.
Note that the warning will appear whether or not newer object types are being used