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

Field is not bound error

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

    Field is not bound error

    On a browse with an Excel export button on the toolbar, the intention is to export the browse to Excel with the settings (sorted and filtered) selected by the user.

    However, one of the columns is a link to the content of a field that stores the address and file name of a file to look up. If not for this column, the browse would export to Excel with no issues. With this column, I get the message "Script a5_browse_export line: 157 Field is not bound".

    There are a couple ways to deal with this. One is to create a custom export that includes all the fields but the unbound one and retains the selected sort and filter as selected. This seems like a lot to do to deal with this error. Another way to deal with this is to bind the field, so the question is whether there is a way to bind the field in such a way that it allows the Excel spreadsheet to be created.

    Yet another solution would be a simple way to exclude just this field from being part of the export, but I'm not seeing this as different from my first observation for a custom export.

    The link column needs to be part of the browse, so it is not an option to remove it from the browse.

    Is there a simple way to make the link field bound to something such that I can export properly? Thank you.

    Jeff

    #2
    Re: Field is not bound error

    If you use a mapped table then fields from both tables appear in Excel.
    On my side anyway, just tried it.

    Comment


      #3
      Re: Field is not bound error

      Originally posted by Ray in Capetown View Post
      If you use a mapped table then fields from both tables appear in Excel.
      On my side anyway, just tried it.
      Sorry, Ray, I don't understand what you mean. All I was saying is that one of my browses has a column defined with a script for each row that runs a procedure when clicked. That column is unbound. I need to either exclude that column or do something that makes it bound. Thanks.

      Jeff

      Comment


        #4
        Re: Field is not bound error

        Originally posted by Jeff Fried View Post
        one of the columns is a link to the content of a field that stores the address and file name of a file to look up. If not for this column, the browse would export to Excel with no issues.

        Jeff
        assumed that the linked field content is a field in a linked table.

        Comment


          #5
          Re: Field is not bound error

          Originally posted by Ray in Capetown View Post
          assumed that the linked field content is a field in a linked table.
          The field with the link address is not necessary to this at all. Not needed in the resulting Excel spreadsheet. The only field in the browse that interferes with a proper export is an xbasic command that calls the content of the link address field. This is "not bound". Neither the xbasic command column nor the link address field are relevant to the export. Do you know of any way to bind the xbasic command column?

          Comment


            #6
            Re: Field is not bound error

            Jeff what, exactly, do you mean by the phrase: "... oneof the columns is a link to the content of a field..." ?

            Sure sounds like you're talking about a field in another table.

            Maybe its time to post an example so we can for ourselves ?

            Comment


              #7
              Re: Field is not bound error

              Originally posted by Tom Cone Jr View Post
              Jeff what, exactly, do you mean by the phrase: "... oneof the columns is a link to the content of a field..." ?

              Sure sounds like you're talking about a field in another table.

              Maybe its time to post an example so we can for ourselves ?
              Fair enough, Tom. Let me do it this way.

              This is a simplification but covers the specifics. I'll call the table with all the data "proposal.dbf". The form with proposal fields is "ProposalForm". When a user is viewing the "ProposalForm" and presses F8, they see "ProposalBrowse".

              The "ProposalBrowse" columns are Sales Rep, Proposal #, Proposal Link, Estimated Amt, Origination Date, Prospect Name, Contact, Status, etc.

              The user will sort and filter, then export to Excel for further analysis or whatever. For example, maybe the filter is by a certain Sales Rep and sorted by Estimated Amt. The export to Excel would normally work instantly without issue except for the column "Proposal Link". "Proposal Link" is not a field in "proposal.dbf". Rather, it uses the data stored in a field of "proposal.dbf" called "linktoprop". The content of "linktoprop" is the location and file name of a file on the network which is typically a document (Excel, Word, PDF, etc.) with information about the proposal. Each row of the column "Proposal Link" has a button title "Get Link". If the user clicks on "Get Link", up pops the stored document from the network location stored in "linktoprop". Below is the code for "Get Link".

              Because of this "Proposal Link" column, the export to Excel does not work. Reason given is that "Proposal Link" is not bound. It is not a field in "proposal.dbf" but exists on the "ProposalBrowse" just for the purpose of the user being able to bring up the stored document for the selected proposal.

              Let me know if this does not clarify my meaning and I'll explain further. Thanks.

              CODE FOR "GET LINK"
              'Date Created: 31-Dec-2013 09:58:12 AM
              'Last Updated: 31-Dec-2013 10:16:33 AM
              'Created By : Jeff
              'Updated By : Jeff
              FUNCTION vmgetlink_ButtonClick AS V ( event AS C, data AS C , row AS N )
              'DESCRIPTION: Fired when a button is clicked on a column.
              'Arguments: event - the name of the event that is fired
              ' data - the data in the column cell
              ' row - the row number in the browse
              'this.SetViewport_Row() sets the current row to the row with the button that was clicked.
              this.Set_Viewport_row(row)
              if .not.isblank("proposal->linktoprop") then
              m_link = proposal->linktoprop
              if file.exists(m_link) then
              sys_open(m_link)
              else
              ui_msg_box("Error Opening File","File '"+trim(m_link)+"' does not exist.",ui_stop_symbol)
              end if
              'ui_msg_box("Response",m_link)
              end if
              END FUNCTION

              Comment


                #8
                Re: Field is not bound error

                Jeff, it sure sounds like the data in the "proposal Link" column IS BOUND to the table supporting the browse.

                I'd try changing the column title to match the actual field name "linktoprop".

                If that doesn't work, I'd try removing the Get Link button(s) that display the data file referenced in "linktoprop".

                If that doesn't work, I'd copy the export xbasic and paste it into a formatted post here so we can see what's going on a bit better. It may be time to use the xbasic to create a custom export that excludes the troublesome column altogether.

                Comment


                  #9
                  Re: Field is not bound error

                  Simplest solution that comes to mind is to append the filtered browse to another table without the unbound field, then export that table to Excel.
                  Alternatively, (and what I would rather do personally) is to save the browse as csv file and import that into Excel.

                  Comment


                    #10
                    Re: Field is not bound error

                    Jeff, I had a similar problem with a browse that included a couple of action buttons on each row to enable a user to enter a payment or go to the detail record for a customer.

                    My solution was to create a second browse with the offending fields omitted which I put on a new form which included an 'export to excel' action followed by 'close window' in the oninit event. I then added a button to the original form to open the new one using the current filter/sort order.

                    Comment


                      #11
                      Re: Field is not bound error

                      I just had this happen on a table I was trying to add a browse button to. I got the button working ok, but on saving the record this error popped up without any other clue as to why. Even on the default browse. It turned out when I checked the index, a deleted record was caught up somehow. A table pack fixed the problem. Hopefully, this might save someone else the HOURS I just spent trying to find out what this error was about!
                      Robin

                      Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                      Comment

                      Working...
                      X