DroidDB Tip of the Month
DroidDB® Tip for June 2015
Dealing With "Action not implemented" When Converting a Visual CE Form to DroidDB
The December 2011 tip-of-the-month (Converting a Visual CE form to DroidDB) describes how to migrate a Visual CE form to DroidDB. But, just because the action of a macro step or button is available in Visual CE, it is not necessarily supported by DroidDB
When converting a macro from Visual CE to DroidDB, the comment of the n'th step of a macro might be converted to an "Action not implemented". Open up the original form in VIsual CE, look at the n'th step of the macro, You'll see what is not implemented.
Likewise, when converting a button from Visual CE to DroidDB, the label on the button might be converted to an "Action not implemented". Again, open up the original form in VIsual CE, look at the button properties, You'll see what is not implemented.
In both cases, the most likely thing that is causing this is a "move to when pressed" action.
Originally, Visual CE had a "move to when pressed" action. Somewhere along the line, we add tabs to the form (because people really wanted them). Tabs and "move to when pressed" are two ways to do, essentially, the same thing...so we didn't put "move to when pressed" into DroidDB.
If your form has multiple "move to when pressed" regions, you can break your form up into multiple forms and change the "move to when pressed" into a "run form". This is a manual process, the conversion tool does not do this.
Top rated! I needed a solid database application development tool for mobile devices. I chose DroidDB for Android OS because it provided a way to get a strong product to market quickly. DroidDB is relational, gives me control over form layout, handles macros, and supports events. It works on all Android versions I have tried and is a great companion product to SYWARE’s VisualCE.
Mark Read, President
SyntegraTech, Inc.
