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

A5 table export to Windows CE, ODBC issues

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

    A5 table export to Windows CE, ODBC issues

    Hi All,
    Is A5V4.5 an ODBC compliant data-source?
    Note: I have been using A5 for a long time and I have a Casiopeia E-125 (Pocket PC), with Windows CE that I want to transfer a table to.
    Do you recommend a software that is compliant with A5V4.5?In my research so far, the HanDbase software needs A5 to be a ODBC complaint data source and seems to be a good choice so far. Any ideas? Recommandations?
    I appreciate your imput,
    Cindy

    #2
    RE: A5 table export to Windows CE, ODBC issues

    Cindy,

    It's my understanding that Alpha Five v. 4.5 stores its data in tables that follow the Foxpro 2.6 format. If your CE device can establish an ODBC connection to Foxpro tables it should be able to get the Alpha Five tables just fine.

    -- tom

    Comment


      #3
      RE: A5 table export to Windows CE, ODBC issues

      Thank you Tom. I will email some of the product designers for Windows CE databases and ask about compatability to FoxPro 2.6 format. That way FoxPro could be used as a sort of conversion program to achieve my Pocket PC objective.
      Thank you for your help. Cindy

      Comment


        #4
        RE: A5 table export to Windows CE, ODBC issues

        You don't need to use ODBC to get a table into a handheld device.

        You can export the A5 table as csv and run a HandDesktop commandline (all within A5) to create the output file that you would then synch to the device. We do this with Palm and IPaq.

        Finian
        Finian

        Comment


          #5
          RE: A5 table export to Windows CE, ODBC issues

          To Finian Lennon:
          That sounds interesting. I know how to export an A5 table as csv, but how do I run a HandDesktop commandline within A5 to create the output file that I would then synch to the device?
          Thanks, Cindy

          Comment


            #6
            RE: A5 table export to Windows CE, ODBC issues

            HandBase has two components, the HandBase database that is installed on the Handheld device and the HandDesktop program that runs on your PC. The command line options for the HandDesktop program are very comprehensive and well explained, with examples, in the online help.

            Finian
            Finian

            Comment


              #7
              RE: A5 table export to Windows CE, ODBC issues

              Sorry, I forgot to mention that you can string the command line options together into a string that you can run via the A5 sys_shell command.

              Here is the part of the code that actually does the HandDesk export
              '=========
              incsv=APP_PATH+"PALMoms_patient.csv"
              pp1=APP_PATH+"PalmHANDDESK.EXE"
              pp2="COMMAND:TOPDB"
              pp3a="PDB:INFILE:{"
              pp3b=incsv+"}"
              pp3=pp3a+pp3b
              pp3aout="PDB:OUTFILE:{"
              outcsv=APP_PATH+"PALMoms_patient.pdb"
              pp3bout=outcsv+"}"
              pp4=pp3aout+pp3bout
              pp5="PDB:DBNAME:{Patients"+off_loc+"}"
              pp6="PDB:HASQUOTES"
              pp7="PDB:OVERWRITE"
              pp8="PDB:AUTOINSTALL:{1}"
              pp9="DB:FIELDNAMES"

              pprun="""+pp1+"""+" ""+pp2+"" ""+pp3+"""+" ""+pp4+"""+" ""+pp5+"""+" ""+pp6+"""+" ""+pp7+"""+" ""+pp8+"""+" ""+pp9+"""

              sys_shell(""+pprun+"",2)
              '===========

              App_Path is a global variable that contains the true (not shadowed) path to our application data. If found it easier to break the command line down as above and then string it back together into thepprun line, which should be all on a single line.

              The above is for the older version of HandBase, substituting HandDesktop.exe for HandDesk.exe should work OK. But there have been some minor changes to the command line in the latest version.

              Finian Lennon

              Finian

              Comment


                #8
                RE: A5 table export to Windows CE, ODBC issues

                Wow!
                I will try this this weekend.
                Hopefully, I will get good results.

                Thank you for all of your help, I'll let you know,

                Cindy Dooley

                Comment


                  #9
                  RE: A5 table export to Windows CE, ODBC issues

                  To Finian Lennon:

                  After reviewing this:

                  ***you can string the command line options together into a string that you can run via the A5 sys_shell command.***

                  I am not a novice in html or basic, however it escapes me as to where specifically I place this code "via the A5 sys_shell command". Can you (please)explain this to me or direct me as to where to start? I sure appreciate everything you have done.

                  Cindy

                  Comment


                    #10
                    RE: A5 table export to Windows CE, ODBC issues

                    I forgot when I posted the message that the board eats backslashes, and there are a lot of those in the script.

                    Attached is a cut from a longer script. It will require some knowledge of Xbasic to follow, but it's n ot that complicated.

                    You could put the code into a button on a form and run it from there, but this code would have to be substantially adapted for the form you use.

                    Finian
                    Finian

                    Comment


                      #11
                      RE: A5 table export to Windows CE, ODBC issues

                      Thank you once again,
                      I'll try to adapt it or "cut and paste" as needed.
                      I appreciate you noticing the backslashes. Have a good weekend,
                      Cindy

                      Comment

                      Working...
                      X