Replace DBF tables with SQL to make SQL tables native to Alpha. Currently the user has to dabble with connection strings. With sql (or MySQL or any other sql) Alpha will be viewed as a complete product instead of just a front end or addon to a back end. I know this is a major undertaking but would be good for Alpha.
This site sucks big time. Users are good. Put us back where we were or at least re-activate the old one so we can choose where to be.
Most of the people who voted to open this menagerie are much newer to alpha than I and others.
Desktop Application buttons are predefined and have specific uses. I think they should be standardized to have Bubble Help as the default, which could be turned off if you want to have text or picture and text. I prefer to have just the icons on the buttons and the mouse-over description. Additionally, I would like to see a series of Button Bars, which would put all of the buttons for any category on the page as a group. ...more »
I would like the dialog2 repeating section to scroll horizontally as well so that i can use more fields than would normally fit onto dialog horizontal extent. of course field names would have to scroll as well.
It is possible:
At least from flickr. Other repositories to be checked.
If you base a grid on an SQL view, then make any change to the view and click the refresh button, the primary key setting is removed. Makes sense because views don't have primary keys, but if I've set one, then don't remove it. Changes are usually not to the primary key field.
Dialog2 has a property to set an argument. We need to be able to assign that with an expression.
In the future, all session variables will be character, but MySQL, for example, typically uses numeric ids, so I'd like to set, for example, argClientid = val(word(session.AllKeys,1,"|")) where session.AllKeys = client id | divistion id | group id | merchant id | location id
Sometimes, I find I need to develop .dll libraries using a high performance compiler that generates native code that used to improve my applications' performance. It would be very helpful to have a high performance xbasic interpreter or, even better, an xbasic just in time compiler built into Alpha Five.
The edit combo lookup builder does not allow you (as far as i can tell) to specify that the Fields to display should be distinct. The result is you can have duplications on the list. Doesn't hurt the selection, but it confuses the user...which one do they pick?
Just thinking it would be nice to have a portable application available. There is a small segment of users who do not have internet available at work or traveling and may not have a laptop available, but still have a need for access to their data. A 'desktop' app that could run from a flash drive would be an ideal solution.
For specifying the filter for the TreeNode, it is often necessary to set a filter at a top level, and then build upon that as you go down the tree - so we have to copy and paste from one window to the next.
Copy and paste buttons would be nice.
I would like a tabular style subform capability in the desktop application in lieu of using a browse.
I wish there was a "preference" setting for tab stops in buttons. When we add a button to a desktop form Alpha automatically assumes we want to be able to "tab" to the button. This is rarely the case for me, so I have to remember to uncheck the tab stop setting in each button I put on a form.