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

Writing to a text file

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

    Writing to a text file

    I am new to Alpha and I need to write data to text files.

    Everything seems to be pretty straight forward but the file create function is telling me that the pointer is the wrong type of file. I realize this is probably obvious but I can't find it.
    I am using the "fnum1" variable for the pointer and I set it to an number. Most basic programming languages use an integer to identify the file pointer.

    Can someone please help me?

    Thanks,

    Patrick

    Below is a program I wrote just to test the function.......





    function DoDistribution as c (e as p)
    ' debug(1)
    dim conn as SQL::Connection
    dim args as sql::arguments
    dim rs as sql::ResultSet

    dim sqlCommand as c
    dim flag as l
    dim CompanyNameID as n
    dim CompanyName as c
    dim DistributorCompanyName as c
    dim LicenseNumber as c
    dim SupportExpirationDate as d
    dim NewSupportExpirationDate as d
    dim ProductCodeCalc as c
    dim Past_Dist as c
    dim Past_Company as c
    dim Basic_Patrh as c
    dim fnum1 as n
    dim fnum2 as n
    dim thefilepath as c
    dim x as n
    dim thetextline as c
    debug(1)

    conn.open("::Name::Connection1")

    'Get the data from the current record that is going to be used for the header record for each quote
    sqlCommand="SELECT Customers.DistributorCompanyName, Customers.CompanyName, Licenses.LicenseNumber, Licenses.ProductCodeCalc, Licenses.NewProductCalcCode FROM Customers INNER JOIN Licenses ON Customers.CompanyNameID = Licenses.CompanyID WHERE (((Licenses.DealerLicense)=False) AND ((Licenses.DemoLicense)=False) AND ((Licenses.SupportExpirationDate)>Date()))ORDER BY Customers.DistributorCompanyName, Customers.CompanyName;"
    conn.Execute(sqlCommand)
    'Get the results of the query and assign them to local variables
    rs = conn.Resultset
    CompanyName=rs.data("CompanyName")
    DistributorCompanyName=rs.data("DistributorCompanyName")
    LicenseNumber=rs.data("LicenseNumber")
    ProductCodeCalc=rs.data("ProductCodeCalc")

    fnum1.file.create("c:\test1.txt",FILE_RW_EXCLUSIVE)

    for x = 1 to 2000
    fnum1.write(thetextline)

    rs.nextrow()
    Next x



    conn.close("::Name::Connection1")

    end function

    #2
    Re: Writing to a text file

    I typically use this method:

    for x = 1 to 2000
    thenextline = "your rs data string goes here"
    lst = lst + thetextline + crlf()
    rs.nextrow()
    next x
    save_to_file(lst,"full path and file name go here")
    Or if you want to use the file pointer, read here: http://wiki.alphasoftware.com/FILE.WRITE+Method
    and use file.write() or file.write_line()

    Read here for all of the file functions and methods: http://wiki.alphasoftware.com/File+F...ns+and+Methods
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Writing to a text file

      I am using the "fnum1" variable for the pointer and I set it to an number. Most basic programming languages use an integer to identify the file pointer.
      The documentation says

      as P = FILE.CREATE( Filename as C, Open_Mode as N )

      So your file pointers need to be dimmed as P.

      Also you probably want fnum1.write_line() instead of just fnum1.write() unless you are after one long line.
      There can be only one.

      Comment


        #4
        Re: Writing to a text file

        Steve,

        Thanks so much for the help!

        Patrick

        Comment


          #5
          Re: Writing to a text file

          Stan,

          Ok, so the pointer needs to be dimmed as the P. That makes sense. Thanks so much for your help!


          Patrick

          Comment


            #6
            Re: Writing to a text file

            Wonder if you get the same result if you try

            'earlier part of script
            rs = conn.Resultset
            txt = rs.ToString())
            save_to_file(txt,"full path and file name go here")
            conn.close("::Name::Connection1")
            There can be only one.

            Comment


              #7
              Re: Writing to a text file

              Stan,
              Not sure...but why can't I store the \ forward slash character in a string?

              dim thepath as c

              thepath="c:\"

              I get an error if the \ is the last character in the string. Any idea why?

              the error is "Expected Value"

              Comment


                #8
                Re: Writing to a text file

                See the documentation for backslash, special meanings.

                You want

                dim thepath as c

                thepath="c:\\"

                or

                thepath="c:"+chr(92)
                There can be only one.

                Comment


                  #9
                  Re: Writing to a text file

                  Stan,

                  Thanks, I really don't like the documentation. Can't find anything I am looking for.

                  Thanks,

                  Patrick

                  Comment


                    #10
                    Re: Writing to a text file

                    I've seen others express the same sentiment.
                    There can be only one.

                    Comment

                    Working...
                    X