Embedded Browses-Blank Records

[[email protected]]

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

[Tbaker]

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

[[email protected]]

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

[Tbaker]

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

[[email protected]]

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

[[email protected]]

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

[Tbaker]

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