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



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

Import the source file name into a field during import.

  • Filter
  • Time
  • Show
Clear All
new posts

  • Import the source file name into a field during import.

    Is there a way to import the source file name into a field during the import process?
    I am importing a file with customer numbers and need to know the name of the file that the information came from. After this file is imported I will append the source file name to another table within my db, using the customer number to merge on.
    Thank You,

    Jamie Powers
    Powers Data Resources

  • #2
    Re: Import the source file name into a field during import.

    The import operation is only able to import what is in the file being imported just as the export operation can only export what exists in a table (can't export an expression based on field values).

    If the structure of the file to be imported is standard you could script adding the name of the file to each record before importing. (ole for excel, file methods for ascii) You could also script an update operation to fill the file name field based on the name of the file being imported.
    There can be only one.


    • #3
      Re: Import the source file name into a field during import.


      Would this update script be included in my import script?

      What I ultimately want to achieve is to populate an image file ref field with the correct file based on the customer number. I am running a scan process(third Party) and OCR to get the customer number, then I am outputing the OCR info to a delimited file, and finally outputing the scan to a jpg file. both of these files have the same file name with the extensions of ".csv" or ".jpg". I need to append the image file ref to the correct record in my db based on a lookup of the customer number from the csv and my db. This project is for data entry of returned response cards and the customer needs the scanned image as well as any information that may be written in by the respondent. Using this method, I hope to allow the scanning to be performed by one department and the record update/data entry to be performed by anyone in the office. If all goes as planned, the data entry person will click a button and all of the newly scanned(not processed) records will pull up in a form with the scan attached and they can make any changes to the record from the scan.
      Thank You,

      Jamie Powers
      Powers Data Resources


      • #4
        Re: Import the source file name into a field during import.

        I need to append the image file ref to the correct record in my db based on a lookup of the customer number from the csv and my db.
        This doesn't sound anything like an append, which creates new records. This sounds like you want to fetch through the records in a table and if you have any records without a filled image reference file field, look in a given directory and see if you can find a .jpg with a matching customer number, and if found place a reference to it in the field.

        Come to think of it, you could create a short script for the cansaverecord event of your table. It would be designed to populate your image reference field (as the record is created) with the proper image reference value which would assume the .jpg was stored in a given directory. Since the image name is known when the customer number is entered, this should be straightforward.

        If the image referenced exists, you're done.
        If the image referenced does not exist, nothing displays.
        When you scan the image with the proper name to the proper directory, the reference is now completed and the image displays.

        I think.
        There can be only one.


        • #5
          Re: Import the source file name into a field during import.

          Thanks Stan

          I didn't look at it this way. I will try this approach it will be much cleaner.
          Thank You,

          Jamie Powers
          Powers Data Resources


          • #6
            Re: Import the source file name into a field during import.

            Just wanted to show what I came up with...I know it's not pretty but it works for me. If there are any suggestions to make this code process multiple files in a loop, it would be great to hear them.

            From this point I would like to tell the UI dialog which directory to use and have it process every ".CSV" file in the directory.
            Thank You,

            Jamie Powers
            Powers Data Resources