xbasic function is not working in alpha five v11 web application

[kalisiddhu]

i wrote xbasic function in the grid component.it is working in one alpha five v11 bulid- 4096,compilers microsoft ccompiler version 1600 OS-window xp.it is not working in another system with same alpha five v11 build 4096,microsoft ccompiler version 1600 software OS-window 7.


function updatingNextCVFeedFollowUpDate as c (e as p)
Dim RequirementName as c
RequirementName=e._currentRowDataOld.Requirement_Name
ui_msg_box("test",RequirementName)
DIM CVFeedBackFollowUpSQLConnection as sql::Connection
if CVFeedBackFollowUpSQLConnection.open("::Name::RMS-Sql") = .F. then
CVFeedBackFollowUpSQLConnection.Close()
exit function

end if
Dim CVFeedBackFollowUpSQLCommandl as c
Dim CVFeedBackFollowUpArgs as sql::Arguments
CVFeedBackFollowUpSQLCommand="update requirements set Last_CV_Feedback_Followup_Date=:NextCVFeedbackFollowupDate where Requirement_Name=:RequirementName"
CVFeedBackFollowUpArgs.Add("RequirementName",RequirementName)
CVFeedBackFollowUpArgs.Add("NextCVFeedbackFollowupDate",e._currentRowDataOld.Next_CV_Feedback_Followup_Date)
if CVFeedBackFollowUpSQLConnection.Execute(CVFeedBackFollowUpSQLCommand,CVFeedBackFollowUpArgs)=.f.
CVFeedBackFollowUpSQLConnection.Close()
exit function

end if
CVFeedBackFollowUpSQLConnection.Close()
end function

[Steve Wood]

Re: xbasic function is not working in alpha five v11 web application .

You did not say what was not working, what error you get or what you expect it to so, so hard to help. But if the problem is that this line fails to work ui_msg_box("test",RequirementName), it is not supposed to work, at all in any web application. UI_ functions are Windows GUI features that work only in a desktop (Windows GUI) environment.

Or if the connection to the sql server fails, I would look at your connection name "RMS-Sql". I have no idea if you can or cannot include hyphens in a connection name, but I would never do it. "RMS_Sql" would be a better name if you need to separate the terms.

Also, just as an aside, your syntax is overly verbose, makes it hard to read and debug. Personal preference of course, you can word it anyway you want, but I would rewrite it as below (I included the proper syntax to show your 'msg box'):

function updatingNextCVFeedFollowUpDate as c (e as p)
dim RequirementName as c
RequirementName=e._currentRowDataOld.Requirement_Name

updatingNextCVFeedFollowUpDate = alert(RequirementName);

dim cn as sql::Connection
if cn.open("::name::conn") = .F. then
cn.close()
exit function

end if
dim vsql as c
dim args as sql::Arguments
vsql = <<%txt%
UPDATE requirements
SET Last_CV_Feedback_Followup_Date=:NextCVFeedbackFollowupDate
WHERE Requirement_Name=:RequirementName
%txt%
args.add("RequirementName",RequirementName)
args.add("NextCVFeedbackFollowupDate",e._currentRowDataOld.Next_CV_Feedback_Followup_Date)

if cn.Execute(vsql,args)=.f.
cn.close()
exit function

end if
cn.close()
end function

[mumfie]

Re: xbasic function is not working in alpha five v11 web application .

it is not working in another system with same alpha five v11 build 4096,microsoft ccompiler version 1600 software OS-window 7.[/B]

Do you get an error message or does the sql update just not update the record you expect.

I would suggest try running it in the debugger but it thats not possible add logging code to log code execution and CVFeedBackFollowUpSQLConnection.callresult.text to a text file
see http://wiki.alphasoftware.com/SAVE_TO_FILE+Function

AFAIK ui_msg_box is NOT supported in web apps.

[SNusa]

Re: xbasic function is not working in alpha five v11 web application .

Do you get an error message or does the sql update just not update the record you expect.

I would suggest try running it in the debugger but it thats not possible add logging code to log code execution and CVFeedBackFollowUpSQLConnection.callresult.text to a text file
see http://wiki.alphasoftware.com/SAVE_TO_FILE+Function

AFAIK ui_msg_box is NOT supported in web apps.

Just a thought, and a totally "moot" issue I suppose: But wouldn't it have been "smart" for the a5 web server to have been designed so that non-functional "desktop based UI code" (like the msgbox()) was "parsed" and converted to it's "javascript equivalent?" When you're forcing the usage of a "proprietary web server" (instead of IIS) & using a non-industry standard development "back-end" language..... One would arguably expect that the a5 web server would have been designed as such.....

[mumfie]

Re: xbasic function is not working in alpha five v11 web application .

But wouldn't it have been "smart" for the a5 web server to have been designed so that non-functional "desktop based UI code" (like the msgbox()) was "parsed" and converted to it's "javascript equivalent?"

javascript would likely be unreliable as it has to be subsequently returned to the client browser to execute. You can however create your own custom javascript to return in many events which will work.
Another option is for WAS to ignore ignore desktop commands but that might result in bugs that are very difficult to trace.

[TheSmitchell]

Re: xbasic function is not working in alpha five v11 web application .

i wrote xbasic function in the grid component.it is working in one alpha five v11 bulid- 4096,compilers microsoft ccompiler version 1600 OS-window xp.it is not working in another system with same alpha five v11 build 4096,microsoft ccompiler version 1600 software OS-window 7.

This is just parroting what Steve suggested. But I would also suggest you return an alert or log the output of your CVFeedBackFollowUpSQLConnection's callResult in the event of either connection or SQL execution failure.

[COLOR="#0000CD"]function [/COLOR]updatingNextCVFeedFollowUpDate [COLOR="#0000CD"]as c[/COLOR] (e [COLOR="#0000CD"]as p[/COLOR])

    [COLOR="#0000CD"]DIM [/COLOR]RequirementName [COLOR="#0000CD"]as c[/COLOR] = e._currentRowDataOld.Requirement_Name	
    
[COLOR="#008000"]    'Replace ui_msg_box("test",RequirementName); it isn't supported on the web server
    'Returns javascript alert box that will be executed client-side
[/COLOR]    updatingNextCVFeedFollowUpDate = [COLOR="#666666"]"alert('"[/COLOR] + js_escape(RequirementName) +[COLOR="#666666"] "');"[/COLOR]

    [COLOR="#0000CD"]DIM [/COLOR]CVFeedBackFollowUpSQLConnection [COLOR="#0000CD"]as sql::Connection[/COLOR]

    [COLOR="#0000CD"]if [/COLOR](CVFeedBackFollowUpSQLConnection.open("::Name::RMS-Sql") = [COLOR="#0000CD"].F.[/COLOR]) [COLOR="#0000CD"]then[/COLOR]
[COLOR="#008000"]        'Return error alert regarding failure to connect
[/COLOR]        *concat(updatingNextCVFeedFollowUpDate, [COLOR="#666666"]"alert('Error opening connection: "[/COLOR] + js_escape(CVFeedBackFollowUpSQLConnection.callResult.text) + [COLOR="#666666"]"');"[/COLOR])
        CVFeedBackFollowUpSQLConnection.Close()
        [COLOR="#0000CD"]exit function
    end if[/COLOR]

[COLOR="#008000"]    'Your original DIM here was CVFeedBackFollowUpSQLCommandl, not CVFeedBackFollowUpSQLCommand
[/COLOR]    [COLOR="#0000CD"]DIM [/COLOR]CVFeedBackFollowUpSQLCommand [COLOR="#0000CD"]as c[/COLOR] =[COLOR="#666666"]<<%SQL%
UPDATE requirements 
SET Last_CV_Feedback_Followup_Date = :NextCVFeedbackFollowupDate 
WHERE Requirement_Name = :RequirementName
%SQL%[/COLOR]

    Next_CV_Feedback_Followup_Date = e._currentRowDataOld.Next_CV_Feedback_Followup_Date

    [COLOR="#0000CD"]DIM [/COLOR]CVFeedBackFollowUpArgs [COLOR="#0000CD"]as SQL::Arguments[/COLOR]
    CVFeedBackFollowUpArgs.Set([COLOR="#A9A9A9"]"RequirementName"[/COLOR],RequirementName)
    CVFeedBackFollowUpArgs.Set([COLOR="#A9A9A9"]"NextCVFeedbackFollowupDate"[/COLOR],Next_CV_Feedback_Followup_Date)

    [COLOR="#0000CD"]if [/COLOR]( CVFeedBackFollowUpSQLConnection.Execute(CVFeedBackFollowUpSQLCommand, CVFeedBackFollowUpArgs) = [COLOR="#0000CD"].F.[/COLOR] ) [COLOR="#0000CD"]then[/COLOR]
[COLOR="#008000"]        'Return alert with information about why the SQL execution failed
[/COLOR]        *concat(updatingNextCVFeedFollowUpDate, [COLOR="#666666"]"alert('Error executing SQL statement: "[/COLOR] + js_escape(CVFeedBackFollowUpSQLConnection.callResult.text) + [COLOR="#666666"]"');"[/COLOR])
        CVFeedBackFollowUpSQLConnection.Close()
       [COLOR="#0000CD"] exit function
    end if[/COLOR]	

    CVFeedBackFollowUpSQLConnection.Close()
[COLOR="#0000CD"]
end function[/COLOR]

[Peter.Greulich]

Re: xbasic function is not working in alpha five v11 web application .

Just a thought, and a totally "moot" issue I suppose: But wouldn't it have been "smart" for the a5 web server to have been designed so that non-functional "desktop based UI code" (like the msgbox()) was "parsed" and converted to it's "javascript equivalent?" When you're forcing the usage of a "proprietary web server" (instead of IIS) & using a non-industry standard development "back-end" language..... One would arguably expect that the a5 web server would have been designed as such.....

It's moot, Robert. As far as I know, the only way to have a desktop app be web convertible is to build it web ready to begin with. And given that Alpha goes way back and the ui_msg_box() and lots of other functionality predate web app popularity, if not the web itself, I don't see how you could expect Alpha to be so clairvoyant as to anticipate that reality and be 100% pre-prepared for it. Silly actually.

[SNusa]

Re: xbasic function is not working in alpha five v11 web application .

It's moot, Robert. As far as I know, the only way to have a desktop app be web convertible is to build it web ready to begin with. And given that Alpha goes way back and the ui_msg_box() and lots of other functionality predate web app popularity, if not the web itself, I don't see how you could expect Alpha to be so clairvoyant as to anticipate that reality and be 100% pre-prepared for it. Silly actually.

Hi Peter;

On one level I agree with you 110%. On the other hand (IMO): The path presently traveled (by Alpha) is continually & effectively "eroding/depreciating the value of xBasic." Instead, Alpha has been adopting & "necessitating fluency" in many different interdependent technologies (without which, a developer cannot "confidently" deliver products "anywhere.") From my point of view, this questions the very reason for AlphaSoftware's existence in the first place. This is not good. ~ And the lack of activity on the forums for their new product seems to seems to reflect this.

PS: I for one really enjoy working with their version of "Basic", more so than with any other variants I have come across. ~ But Alpha's recent offerings leave me thinking "what's the point?" (And I think that's the problem for a lot of us as we look at the alternatives.)

[Steve Wood]

Re: xbasic function is not working in alpha five v11 web application .

Its a question of where do you stop. Alpha already has lots of xbasic that reproduces traditional non-xbasic functions. I am thinking about Portable SQL, Action Javascript, and other "helper" functions. But really, software development requires expertise in multiple areas. Do you want Xbasic to replace CSS, Javascript, SQL, etc.? Where would you stop? And why should I purposely degrade my skills and marketability as a web application developer by learning an Xbasic method that obscures for me the most common, accepted method by all other developers. As an A5 web developer I have been forced to also learn HTML, CSS, SQL, Javascript, JQuery, carbon dating, and other 3rd party tools. If Alpha had an Xbasic function to replace each of those, would I be better off using Xbasic or the native resource? If you were a paying customer of mine, would you want me to ONLY know Alpha Five? It is the integration of resources not a replacement that makes Alpha Five a useful tool.

[SNusa]

Re: xbasic function is not working in alpha five v11 web application .

Hi Steve;

I realize this thread became "way off topic", but not a big deal since the OP's question was answered in the first few posts.....

Where would I stop? Given Alpha's 20+ years of marketing Alpha as the tool for everyone including "non programmers", the answer is fairly simple: Use the KISS method. 1 layer for SQL/database integration (AlphaDAO) for database integration, and 1 for coding (xBasic.) (with a touch of exposure to javascript for the web) Too much beyond that and I think they end up catering to a new audience that doesn't exist in any significant numbers..... I suspect that most software developers (with a "high-end" well rounded skill set like yourself) are going to choose industry standard tools to minimize risk. (unless there are huge benefits elsewhere) ~ In this regard, AA has arguably lost most of it's significant advantage(s). Obviously everyone is entitled to their own opinion. In the end, the mighty $ will do the voting & dictate the future.

I do agree with your statement, but only for those who wish to develop ONLY for the web and for those who ALREADY have a strong background in xBasic. Even so, the fact one chooses AA mandates that they must use (at the core), a proprietary language along with a very "unique & expensive WAS."

Irrespective, 20+ years was invested in marketing a5 to those who wanted things to be simple and under one roof. It's purpose of existence (to much of the user base) was originally to enable non coders to code. (And then grow with the tool as their skill levels grew.) At present, much of their existing desktop user base has been left with the feelings of "abandonment." (Even more so since v.11 now suffers from the recent update to ie.11, and no v.11 updates are seemingly forthcoming to address this.) ~ In this regard, Alpha isn't even "kicking the dead horse", they are "kicking the rider" instead.

My questions for you are: Would you encourage "a newbie" to pick up AA instead of another tool? And if so, why? (And would you even consider suggesting v.12 (AA) for those who wish to produce desktop/lan applications?) Finally (without an update to fix v.11 with regards to ie11 breaking the web desktop tools), hasn't the sun "already set" on v.11?

PS: The recent ie11 update (which resulted in the the "breaking" of v.11 web tools on the desktop) is the very reason I have always thought of this kind of approach/solution/dependencies to/for/of desktop development as being "undesirable" at best. I do understand the reasons for "settling" on one standardized presentation level. ~ But at what costs?