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

SQL permission issue?

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

    SQL permission issue?

    AA running on one server in a domain, SQL Server running on another box in the domain. When I try to load data that is saved on the AA box using a script in AA, I get the attached error. F: is a mapped drive on both boxes. If I run the same code in SSMS on the SQL box it works fine. So the file can certainly be seen from the SQL box. This is the code.
    Code:
    BULK INSERT Client
    FROM 'F:\Data\Warrants\sqlcsv_client.csv'
    WITH
    (  FORMATFILE = 'F:\Data\Warrants\sql_Client_Mod.fmt'
    )
    I have tried both windows credentials and sa account in the AA connection string.

    From AA I can run a script that creates the SQL tables and that works fine, but it does not need to read any files back on the AA box.

    Not sure it is really a permission issue?

    Bill.
    Attached Files

    #2
    Re: SQL permission issue?

    42000 is a syntax error, or using a reserved word in your script, files or tables.
    Ferret about with reserved words.
    See our Hybrid Option here;
    https://hybridapps.example-software.com/


    Apologies to anyone I haven't managed to upset yet.
    You are held in a queue and I will get to you soon.

    Comment


      #3
      Re: SQL permission issue?

      I tried using a UNC path vs. the mapped drive. Import was successful with a UNC path, e.g. '\\FS1\Alpha\Data\Warrants\sqlcsv_client.csv'. So the question now is if it is possible to get the mapped drive syntax to work.

      The path is dynamic and can change a lot, so get_path() is used. get_path() does not produce UNC, so not sure how to get there.

      Bill.

      Comment


        #4
        Re: SQL permission issue?

        Could you use a combination of API_GETMACHINENAME and GET_PAth to build the UNC? Would need to make sure the path includes a valid share with the same name as a directory in the path on the AA server.

        BTW, why posted in the desktop forum?

        Comment


          #5
          Re: SQL permission issue?

          The problem is getting the part of the path in the mapping - \Alpha. There may be some way to get the mapped definition from Windows? But a new problem is confounding me. There is a CSV file in another folder that is giving an error on the UNC path! The UNC path gives "access denied". The mapped path gives "can't find path specified". Loading the file from the original UNC path sill works. And the code still works in SSMS either way.

          This is so confounding that I don't think it is solvable on the message board, unless there is some thought on the original question of a mapped path not working.

          (This app is converting from desktop to web. I put it in desktop since this export part is technically still desktop.)

          Bill.

          Comment


            #6
            Re: SQL permission issue?

            If the missing bit is always Alpha, just hardcode it...

            path = "\\" + api_getmachinename() + "\Alpha" + substr(a5.Get_Path(),3) + "\"

            Comment


              #7
              Re: SQL permission issue?

              I think this gets a list of mapped drive letters and their corresponding UNC paths. (Win 7)

              Code:
              FUNCTION unc_list AS C ( )
              'get drive letters
              writs = a5_get_writeable_drives()
              writs = strtran(writs,":\\","")
              'check for remote paths
              pairs = ""
              for each drv in writs
              	unc_chk = Registry.sys_get("HKEY_CURRENT_USER\Network\\"+drv+"\RemotePath")
              	if unc_chk > ""
              		pairs = pairs+drv+"~~"+unc_chk+crlf()
              	end if
              next
              unc_list = pairs
              END FUNCTION
              There can be only one.

              Comment


                #8
                Re: SQL permission issue?

                Stan, you are amazing!

                What comes after gold watch?

                Comment


                  #9
                  Re: SQL permission issue?

                  In another thread Lenny said there may be a problem with the sql connection not having permissions to read files remotely. I don't know if there is any solution to that, so I have changed the output location when creating the CSV file. I was dreading having to convert all my export operations to code so the path could be easily changed. Ended up with this and thought I would share.
                  Code:
                  'export.run_silent(exportname, vFilter)  'run_silent does not have an xbasic option
                  
                  xbcode = export.run(exportname,".f.","",.t.,.t.)	'this gets the xbasic so I can change filename. runs silently.
                  xbcode = stritran(xbcode, "export.file = export_filename", "export.file =" +quote(csvfilename))
                  xbcode = stritran(xbcode, "query.filter = a5_operation_filter", "query.filter =" +quote(vFilter))
                  evaluate_template(xbcode)
                  I now write the CSV to the SQL box so the Bulk Insert has no problem.

                  Bill.

                  Comment

                  Working...
                  X