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

Embedded Browses-Blank Records

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

  • Tbaker
    replied
    Re: Embedded Browses-Blank Records

    Tom

    The only thing I can say now is can you zip that test table that works off and on so I can get a look at it to see what might be happening.

    I have run across some very crazy things with Version 9 in the past but I no longer have any apps running in that version. I have converted all but one to Version 10.

    Tom, just try this

    In the forms on activate event, instead of going directly to the browse, have it go to one of the buttons. Or you could just create a temporary session variable and insert that on the form and activate that or a button when you open the form.

    See if that changes things (this is just a temporary thing - not a workaround)

    I would still like to see a sample if you can arrange it.

    Tom Baker

    Leave a comment:


  • tom@statesidedata.com
    replied
    Re: Embedded Browses-Blank Records

    Tom,

    I don't know what's going on here. The behavior is erratic. Sometimes it works correctly, sometimes it doesn't. I don't know what's going on.

    The thing is, the table only has 2 fields. Both of the fields are indexed. The browse sorts in ascending order on the mfg name. That's all there is to it.

    What makes this whole thing important to solve is that I have 16 other tables just like this one. I use these tables as "codes" for user defined lookups.

    ?????

    Tom

    Leave a comment:


  • tom@statesidedata.com
    replied
    Re: Embedded Browses-Blank Records

    Tom,

    OK, this is getting stranger by the minute.

    I created a stand alone browse from the mfg table and inserted that browse in a copy of the form you see above. It behaved perfectly. A single record was temporarily created, but when I left the form, Alpha asked if I wanted to save it, I said no and the record was gone.

    So, at that point, the table was still empty.

    Now, I went back into the original form and, sure enough, 3 new blank records were generated.

    The only difference I can tell is that the original form has an embedded browse in it, while the working form has an external browse. Nothing else is any different.

    Wait a minute...the external browse does not work properly anymore. I'm checking on some of the things I changed...

    What do you think?

    Tom
    Last edited by [email protected]; 09-16-2010, 01:22 PM. Reason: changes needed

    Leave a comment:


  • Tbaker
    replied
    Re: Embedded Browses-Blank Records

    Tom

    If the table is empty - when you open the form, the autoincrement field will be filled immediately without asking or selecting add record.

    Controlling record insertion with a browse, is at time difficult. It only take navigation from that record to commit the record (without asking).

    Can you create a test form (as I did) with the buttons on a form, and see if it does the same thing.

    With the test form I created with the two fields, it worked properly but then again I did not have the buttons on the form.

    One other question, is there an event in the field rules - just a wild stab in the dark?

    I can't duplicate what you are seeing so a sample you create that shows the problem would be helpful.

    Tom Baker

    Leave a comment:


  • tom@statesidedata.com
    replied
    Re: Embedded Browses-Blank Records

    Tom,

    Thanks for your response.

    I checked everything. There are no form events firing. The buttons are all vanilla.

    Delete: deletes and then goes to first record
    Print: prints
    Return: save parentform.commit(), close form, open a new form
    Home: save parentform.commit(), close form, open a new form

    But keep in mind that the form opens with the 3 blank records added. There don't pop up after I have pressed a button.

    Now I do have auto increment set to "on" in the field rules but that shouldn't generate 3 records...possibly one, but I'm thinking that not even one would be generated until I press ADD a record.

    Thanks,
    Tom

    Leave a comment:


  • Tbaker
    replied
    Re: Embedded Browses-Blank Records

    Tom

    As I am sure know that if you have a empty table and you open the form, the form will be enter mode - and looking at your thumbnail, the mfg_id is an autoincremented field so the id is placed in the first field in the first row.

    Do you have any form events such as OnInit, OnActivate, OnFetch, OnEnter, OnSave and the Can events?

    It would seem that the form when opened is placing the autoincrement field and some code (somewhere) is issuing a commit().

    What is the code behind the buttons on the bottom of the form. Do any of them either issue a parentform.commit() or code to navigate away from the first record in the browse?

    These are just guesses on my part.

    I created a test form with two fields matching your two fields with autoincrement on the mfg_id field. I then created a menu to load that form. It opens with the incremented field showing the proper id and it then waits for input. It does not create two additional records.




    Tom Baker

    Leave a comment:


  • tom@statesidedata.com
    started a topic Embedded Browses-Blank Records

    Embedded Browses-Blank Records

    A few weeks ago I posted a similar problem to the one I'm about to describe, but this situation is different and I can't figure it out. Here's what's happening.

    I have a very simple form constructed around a single table and the form uses an embedded browse for adding, changing and deleting records. It works fine except...

    When I begin with an empty table and bring up this form, it adds three blank records. Of course the blank records can be deleted or edited, but this shouldn't be happening.

    I have checked the form and have turned off Continuous Enters and that doesn't help. Since I have to have Enter, Change and Delete functionality I cannot turn these off. However, just to see what would happen, I did turn off Enter mode at the browse level and it still addded 3 blank records. Nothing I do seems to make a difference: 3 blank records are always added when the table is empty...after that it behaves properly.

    I'm also wondering why the number is 3, although this really doesn't matter much.

    Thanks for any answers here.

    Tom
Working...
X