trouble with portal and deleting rows

#1

Hello all,

Apologies for a quasi-newbie question on portals. I'm using Filemaker
8.0v1 on OS X and linked two tables via an auto-incrementing ID field.
I then set up a portal so that I could associate multiple tasks with
the same project (the fields for the portal come from the first table).
The portal has a button at the end of the line to "Delete
Record/Request" (I also tried setting it to "Delete Portal Row") so
that an individual task could be deleted. The portal seems to work, in
that I can create multiple task items for each record. But as to the
delete button, sometimes it works properly and just deletes the
selected portal line item, and sometimes it deletes the entire
Filemaker record! This has me thinking there's something wrong with
the portal setup (as opposed to a bug with the delete function).

One thing I did was look at the ID that's getting associated with each
portal entry, and it appears that every portal item associated with a
record has the same ID #, and the next record's ID # starts a few
numbers higher. Sometimes it starts 2 numbers higher, sometimes 3, and
I can't figure out exactly how it's deciding to do the incrementation.

I'm not sure I've worded my problem clearly enough or provided enough
information for troubleshooting purposes, but any thoughts y'all have
would be appreciated!

#2

In article <1132288220.151337.37310 (AT) g14g2000cwa (DOT) googlegroups.com>,
jbpollock (AT) gmail (DOT) com wrote:

Quote:

Hello all,

Apologies for a quasi-newbie question on portals. I'm using Filemaker
8.0v1 on OS X and linked two tables via an auto-incrementing ID field.
I then set up a portal so that I could associate multiple tasks with
the same project (the fields for the portal come from the first table).
The portal has a button at the end of the line to "Delete
Record/Request" (I also tried setting it to "Delete Portal Row") so
that an individual task could be deleted. The portal seems to work, in
that I can create multiple task items for each record. But as to the
delete button, sometimes it works properly and just deletes the
selected portal line item, and sometimes it deletes the entire
Filemaker record! This has me thinking there's something wrong with
the portal setup (as opposed to a bug with the delete function).

Your "Delete" button should be inside the portal's frame and only one
button is needed inside the first portal row (when in layout mode).
eg.

[ PortalField PortalField PortalField DeleteButton ]
[ ]
[ ]

The button will replicate itself as new records appear in the portal.
The button should be set to "Delete Portal Row" and then it can't
possibly delete the parent record.

Note: If the relationship the portal uses is set to allow the creation
of related records, then the portal displays a blank row at the bottom
and this too will be given a "Delete" button even though there is no
actual record there. There are ways around this, but if it doesn't
worry you why bother?

Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)

#3

Harry (and others),

I actually had put the button inside the portal's frame and only used
one delete button exactly has Harry described. The button had been
replicated exactly as Harry described, and was set to "delete portal
row". And yet pressing this delete button on one particular row causes
all of the rows to be deleted as well as the main record itself.
That's why I'm baffled. This is what makes me think I've made some
mistake in the portal setup.

#4

I should add again too that it doesn't *always* delete the entire
record. I just created a record and added three tasks in my portal. I
then hit the delete key to delete one, and it properly disappeared
without affecting the other rows of the portal. I then browsed around
to some other records, then came back to that record and deleted a
second row. This time it deleted the entire record.

#5

jb

The deleting should work, are you actualy deleting through a script or do
you have the delete directly connected to the button?

I'm willing to have a look at it. But need your file(s), could you empty
them, stick a couple of example records in them. Then zip them and put them
on a hyperlink (in your web-site) so I could download them and have a look
what is wrong. You can also use www.yousendit.com to send large files (or
send them directly if they are not that big)

ursusDOTkirkATwanadooDOTnl

Ursus

<jbpollock (AT) gmail (DOT) com> schreef in bericht
news:1132316556.040621.176530 (AT) g43g2000cwa (DOT) googlegroups.com...

Quote:

I should add again too that it doesn't *always* delete the entire
record. I just created a record and added three tasks in my portal. I
then hit the delete key to delete one, and it properly disappeared
without affecting the other rows of the portal. I then browsed around
to some other records, then came back to that record and deleted a
second row. This time it deleted the entire record.

#6

I've deleted all the records in the database, created a few dummary
records, and uploaded the database to http://jpollock.web.wesleyan.edu.

The problem is in the Tasks layout, with the tasks portal in the middle
of the page.

#7

Whoops, make that "dummy", not "dummary".

Thanks all for your help with this, and thanks Ursus for offering to
take a look!

#8

jbpollock (AT) gmail (DOT) com wrote:

Quote:

I've deleted all the records in the database, created a few dummary
records, and uploaded the database to http://jpollock.web.wesleyan.edu.

The problem is in the Tasks layout, with the tasks portal in the middle
of the page.

You need to go into database setup and then relationships, then uncheck

the boxes to allow creation of related records and delete records in
this file when a record in the related file is deleted from the parent
side of the relatioship.

Michael Myett