Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Keeping a Form with drop/add to dbf

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Keeping a Form with drop/add to dbf

    I'm trying to pull sql data to a temp table that will be overwritten everytime the sql query is ran. I want to make a form to work the table which i'm thinking that i have to design it in the script , when i design the form within the script it opens unsaved and in design mode. Here is the sql code i'm starting with
    Code:
    DIM cn as SQL::Connection
    dim flagResult as l 
    flagResult = cn.open("::Name::*****.net")
    if flagResult = .f. then 
    	ui_msg_box("Error","Could not connect to database. Error reported was: " + crlf() + cn.CallResult.text)
    	end 
    end if
    
    'Specify if you are using Portable SQL syntax, or not
    cn.PortableSQLEnabled = .t. 
    dim sqlStatement as c 
    sqlStatement = <<%sql%
    SELECT FIRST 1 custid, custfullname, fname, lname, address, city, state, zip, Dispo, findone, repid, called, cid, erollapdone, phone, notes_custid, callnote, payinfo, recentmtgamt, loanorigdate, recentlender, recentloantype, loantoval, age, creditrating  FROM custinfo  WHERE (phone IS NOT NULL ) AND (called IS NULL )
    %sql%
    'Execute the Query
    flagResult = cn.Execute(sqlStatement)
    if flagResult = .f. then 
    	ui_msg_box("Error",cn.CallResult.text)
    	cn.close()
    	end 
    end if 
    dim rs as sql::resultset
    rs = cn.ResultSet 
    
    resultP = SQL_QueryImport(cn,sqlStatement,"C:\ahtdialer\tst.DBF")
    'Execute a query on a SQL database
    'DIM a connection variable
    
    'Now, dump the contents of the ResultSet to a variable
    dim qpoint as c 
    qpoint = rs.ToString()
    
    'Now, close the connection 
    cn.close()
    i've tried to design the form and then run the script but it deletes the form when the table is overwritten
    https://www.housingeducator.org
    k3srg

  • #2
    Re: Keeping a Form with drop/add to dbf

    You'll probably have to have a destination table upon which the form is built and empty the table each time you run the script. You would then append from the temp table to the "real" table.
    There can be only one.

    Comment


    • #3
      Re: Keeping a Form with drop/add to dbf

      Originally posted by Stan Mathews View Post
      You'll probably have to have a destination table upon which the form is built and empty the table each time you run the script. You would then append from the temp table to the "real" table.
      I was thinking that would have to be the way. trying to cut query time.
      https://www.housingeducator.org
      k3srg

      Comment


      • #4
        Re: Keeping a Form with drop/add to dbf

        Ok so i have managed to send the results to dbf and then append them to another static table and now i can't seem to figure out how to run an sql update record based on a var.
        when i read the xbasic not sure how to set the txt string. Here is what i have.
        Code:
        'Get 'Value' property of 'Custid' in Form 'TST2' .
        DIM SHARED CUST AS c
        CUST = parentform:Custid.value
        'Update a record(s) in a remote SQL database.
        'DIM a connection variable
        DIM cn as SQL::Connection
        dim flagResult as l 
        flagResult = cn.open("::Name::stevengreer.net")
        if flagResult = .f. then 
        	ui_msg_box("Error","Could not connect to database. Error reported was: " + crlf() + cn.CallResult.text)
        	end 
        end if
        
        'Specify that we are using Portable SQL syntax
        cn.PortableSQLEnabled = .t.
        
        'Dim a SQL arguments object, create arguments and set their values
        DIM args as sql::arguments
        
        if a5_eval_valid_expression("=Var->user",local_variables()) then 
        	args.add("New__called",convert_type(a5_eval_expression("=Var->user",local_variables()),"C"))
        end If
        
        
        dim sqlUpdateStatement as c 
        sqlUpdateStatement = [COLOR="Red"]<<%txt%
        UPDATE custinfo SET called = :New__called  WHERE custid = 'cust'
        %txt%[/COLOR]
        
        dim flag as l 
        flag = cn.Execute(sqlUpdateStatement,args)
        if flag = .f. then 
        	ui_msg_box("Error","Record was not updated. Error reported was: " + crlf(2) + cn.CallResult.text,UI_STOP_SYMBOL)
        else
        	if cn.AffectedRows() > 0 then 
        		ui_msg_box("Notice", "" + cn.AffectedRows() + " record(s) updated.",UI_INFORMATION_SYMBOL)
        	else
        		ui_msg_box("Error","Record was not updated." ,UI_STOP_SYMBOL)
        	end if 
        end if 
        
        'Now, close the connection 
        cn.close()
        https://www.housingeducator.org
        k3srg

        Comment


        • #5
          Re: Keeping a Form with drop/add to dbf

          Steve, you may have better exposure for your new question if you start a new thread. It also helps others later to find threads relevant to the issue.

          Re your original question.

          You can also try creating a set and only include the one table. Sounds a bit useless to only have one table in a set because it won't be set of anything.

          But the forms and reports etc will be stored in the .se* files of the set instead of the .dd*. When the table gets completely replaced then the set will still be pointing to that table and its data.
          Tim Kiebert
          Eagle Creek Citrus
          A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

          Comment


          • #6
            Re: Keeping a Form with drop/add to dbf

            Thanks Tim that sounds
            like a simple clean way to get past form pointers
            I'll check it out and see if it works
            for
            me
            https://www.housingeducator.org
            k3srg

            Comment


            • #7
              Re: Keeping a Form with drop/add to dbf

              Originally posted by Tim Kiebert View Post
              ...You can also try creating a set and only include the one table. Sounds a bit useless to only have one table in a set because it won't be set of anything.

              But the forms and reports etc will be stored in the .se* files of the set instead of the .dd*. When the table gets completely replaced then the set will still be pointing to that table and its data.
              Bravo! Great idea!

              So simple. So obvious once you think about it. Yet not something most people (including me) would think of right away.

              Comment


              • #8
                Re: Keeping a Form with drop/add to dbf

                Doing that with QReportBuilder (QRB) and QuickBooks is something that is almost a necessity as Passive linked tables are being used. In fact this is what Alpha did when creating QRB---any report data brought over from QuickBooks is placed into a new table that is actually as Tim states...a set of one table.

                Another way of course is to duplicate the table, not having it Passive or Active linked, and then append to it from the tables that are recreated as such when new data is brought across.
                Mike
                __________________________________________
                It is only when we forget all our learning that we begin to know.
                It's not what you look at that matters, it's what you see.
                Henry David Thoreau
                __________________________________________



                Comment


                • #9
                  Re: Keeping a Form with drop/add to dbf

                  Originally posted by CALocklin View Post
                  Bravo! Great idea!

                  So simple. So obvious once you think about it. Yet not something most people (including me) would think of right away.
                  Yeh, would love to take credit for that great idea. But alas, it did not come from I. Not sure where I first saw it. I think it was one of the Steves from which I gleaned this little gem.

                  Cal,
                  I love you smilies.
                  Last edited by Tim Kiebert; 03-30-2010, 05:19 AM.
                  Tim Kiebert
                  Eagle Creek Citrus
                  A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                  Comment

                  Working...
                  X