Alpha Developers Network

Guest


Recent Posts

Pages: [1] 2 3 ... 10
1
Best Practices / time stamp
« Last post by rich the lock on August 14, 2017, 07:34:08 PM »
Is this forum still on? j/k

I'm having some trouble creating a time stamp in Alpha. I have created a field in MySQL that is a timestamp field. When it comes to my UX control, I'm still unsure of where to put the javascript(if any), and which lines of code to use. I've tried multiple variations I've pulled off of Javascript websites, but my lack of knowledge in JS is tripping me up. Can anyone out there help?
2
Alpha Web Application Server for IIS / IIS lag issue - internet monitor utility
« Last post by JChasko on August 04, 2017, 10:55:26 AM »
In the IADN user group meeting today, a problem with IIS lag was discussed. Perhaps something mysterious in Microsoft server overhead, or connectivity. There is a very simple Windows utility that logs excessive ping times to three different sites. Sometimes Speedtest.net or Fast.com will report reasonably high transfer times while lag can be excessive. At any rate, it provides a log to get your ISP to fix persistent issues.
https://netuptimemonitor.com/
3
Jim Coltz - JQuery Calendar / Re: starttime and endtime not being saved properly
« Last post by Jim Coltz on March 04, 2017, 08:46:34 AM »
I am happy to hear you have it sorted out.
4
Jim Coltz - JQuery Calendar / Re: starttime and endtime not being saved properly
« Last post by Laurencia on March 04, 2017, 08:44:10 AM »
After further experimentation, it appears your theory is correct.

Thank you.
5
Jim Coltz - JQuery Calendar / Re: starttime and endtime not being saved properly
« Last post by Laurencia on March 04, 2017, 07:53:12 AM »
The MySQL table was created using the MySQL script at http://www.a5customsolutions.com/jqcalendar_docs.html

The table columns are StartTime (datetime) and EndTime (datetime).

onDialogInitialize has dim e._state.separate_date_times set false

Is the above as required?

6
Jim Coltz - JQuery Calendar / Re: starttime and endtime not being saved properly
« Last post by Jim Coltz on March 04, 2017, 07:28:26 AM »
It sounds like the data binding for the UX is not set up correctly. Please verify your mapping. Note that the mapping is dependent on whether your back-end is using separate date and time columns or date-time columns. Also verify that the back-end database is configured to match.
7
Jim Coltz - JQuery Calendar / starttime and endtime not being saved properly
« Last post by Laurencia on March 03, 2017, 08:35:21 AM »
Upon entry of a new record (from the detail/edit UX form, in LivePreview mode), the INSERT (MySQL) fails apparently due to missing (wrong format) data:

:jqcalendar_starttime (T) 10/22/2017 12:00:00 00 am
:jqcalendar_endtime (C) 10:37 am

1292 - 'Incorrect datetime value: '10:37 am' for column 'EndTime' at row 1'

Where the DATE portion does exist, the TIME seems to be getting submitted as the DATE, and the time is always 12:00:00 00 am regardless of setting in the form.  Why is the datatype showing T on starttime, but C on endtime?

This is quite confusing.

Often, the Date portion is missing altogether (although the time is then properly submitted as the time).

The jqcalendar.aex file is dated 8/31/2015
8
Alpha Web Application Server for IIS / Re: Project, locked into IIS?
« Last post by KatiBruce on September 16, 2016, 07:11:11 PM »
Hi all,

I can confirm The we have a couple of projects where we publish to BOTH WAS and IIS (both are running on the SAME server). In our case we use the WAS as the Beta site and when the Client is happy then we publish to the IIS (LIVE) site. WAS is on port 8080 and IIS is on port 80. 
On the codeing side there have been a few things that we had to change to get to work on IIS (can't think what they were now) but not too many things in the grand scheme of things.
9
General Discussion / Alpha Licensing changes
« Last post by Steve Wood on September 08, 2016, 01:58:44 PM »
<< From Selwyn

I think the real issue here is that we expect customers to have a valid subscription at all times.

For historical reasons, the legacy customer base (i.e. customers who were v11 users before V12 came out) have a special type of subscription that allows them to continue using the product after their subscription end (but limits them to the last official build that was available at the time their subscription ran out)

we no longer sell these types of subscriptions anymore.

we only sell 'true' subscriptions which means you must have a valid subscription at all times in order to use Alpha Anywhere.
>>

<<
Clarification by Lenny:
Selwyn's explanation of licensing was already posted in this thread. I cannot comment further on license offerings or policies, but I can attempt to clarify his statement.

Alpha Five Version 11 and prior licenses are all perpetual licenses. If you own one of these licenses, you may use that software indefinitely.

Alpha Anywhere (V12) is subscription based and the subscriptions have had 2 different models:
Initial Alpha Anywhere subscriptions included a perpetual license that allowed indefinite use of the software, up to the last official release available when the subscription expires. If the subscription expires and the software is newer than the latest official release available on the expiration date, the software will not work. This can be resolved by applying an older patch.
Current Alpha Anywhere subscriptions do NOT include a perpetual license. When the subscription expires, you will be unable to use the software. This is the only type of subscription that is currently offered. Your data is yours and will not be locked or blocked in any way, but you will not be able to use Alpha Anywhere to access it.


The second type of subscription (without a perpetual license) is the only subscription currently being offered by Alpha Software. All new subscribers will have this type of subscription.

If you do not know which type of subscription you have, you can contact your sales rep directly or email sales @ alphasoftware.com. Similarly, contact sales if this explanation is still unclear, or if you are interested in some type of custom license offering.

Quote Originally Posted by lgrupido  View Post
While you are at it - a proposal for how to handle subscriptions that expire on dates and/or times someone from Alpha is not available to renew a subscription (or maybe a link to a site where we could make a renewal online) would also be appropriate. I can recommend a software product that would make such an online payment quite easy.
Regarding the ability to renew at any time, this is something that is in process. There will be an online portal where you can view your existing subscriptions and renew them directly. Taking the online payment is the easy part, what is missing is the integration with the licensing system to allow the payment to immediately extend a subscription. Unfortunately there is no firm ETA for the roll-out of this.
>>


10
Alpha Web Application Server for IIS / Answers/Clarification to some questions
« Last post by TheSmitchell on September 08, 2016, 12:55:31 PM »
Hello everyone!

I wanted to answer some questions/concerns that have come up during the IIS sessions.

Is the Alpha Anywhere Application Server for IIS still in beta?

NO. The Alpha Anywhere Application Server for IIS is no longer in beta.

If I convert my Alpha Anywhere Standard Application Server license to an Alpha Anywhere Application Server for IIS license, will my Standard server be shut down immediately?

NO. Alpha will work with you to provide you with a migration window that will give you the time you need to move your applications from the Standard server to the IIS server.

If I publish an application to the IIS server, can I publish the same application to the Standard server?

YES. You can publish to both. And PhoneGap. And Alpha Cloud.

Can I run both the IIS server and Standard server with one license?

NO. In order to run both the IIS server and Standard server, you need a separate license for each.



If you encounter any problems when trying to publish your application to IIS through Alpha's publishing utilities, tell us. Contact us at a5v12bugs@alphasoftware.com so we can help you.

You can find documentation about the IIS server in our help documentation. This documentation includes information on how to setup and configure IIS as well as how to migrate an existing Alpha Anywhere application to IIS. If you find any problems with the documentation, you can report them to the documentation team at documentation@alphasoftware.com.



Finally, if any of you will be attending DevCon this year, bring your IIS questions! Terry will be available to answer any IIS questions you may have.

Thanks and good luck!
Pages: [1] 2 3 ... 10