I have a table view subform  on a tab that I use to create a new subrecord. The jist of the programming section that handles this is like this:

nn = @FormNewRecord("payments")
FormFieldValue("payments", "transaction_date", nn, @date)
FormFieldValue("payments", "transactionType", nn, TempTransType)
FormFieldValue("payments", "paymentamount", nn, TempTransAmount)
FormFieldValue("payments", "Paymentdate", nn, TempPaymentDate)
FormFieldValue("payments", "Paymentchknum", nn,  TempchecknumDate)
FormFieldValue("payments", "TransactionNote", nn,  TemptransactionNote)
FormFieldValue("payments", "Billed amount", nn, "0")

I only want the user to be able to affect the table view subform (a basic payment and billing ledger) via my programmed fields so I set the subform element to read only. This works fine until more data is posted then the subform element size. In read only  I am not able to use the subform sizing arrow bar to scroll down.

Is there a way to allow the sizing arrows to be active even in read only?

One method that solves this problem is to leave the subform NOT read only and set the elements in the database the subform is made from to read only. This allows the scroll bars to work while protecting the element data with read only capabilities.

The problem with this method  is I was planning on having a manager feature that temporarily makes my subform Not read only so they could easily correct or manage the data from the subform. I know how to easily change the read only attribute of the subform with Sbasic, but I am not sure if my attribute commands will allow me to temporarily change attributes on a different form in a different database.

Any Thoughts?

Thanks

How about put all "Read Only" elements on same level (Version 2), then make that level ReadOnly vs. time to do loops?

In a very recent Inside Sesame article jointly penned by Tom Marcellus and myself, we described this exact scenario. We reckon the way to do it is to make each subform element read-only and keep it that way, but provide buttons and 'mirror' elements on the parent form for manipulating the subform records as required. This way you can do whatever you want security-wise on the main form, provide unbound elements to show the data from a specific subrecord, and allow the user to edit that record or delete it. Oh and records can only be added this way too. The subform is visible only for convenience, to view multiple records. The subform can even be invisible, permanently and I have an app that does this. The article is "Managing Table View Subforms" in the May 2007 edition of Inside Sesame.

Alec and Toms Example in the Inside Sesame article was terrific. It works very well. I tried (but failed) cannibalizing the same code to do a similar task. Instead of modifying the data based on the users selection of the subform record I wanted to use some of the data in the subform with a MergeFilePrint() command.

My thought was when a print reminder command button was selected  I would present the user with a popup selection of the subform records and have them select what record in the subform would be used to grab the data to create the merge file.

My subform is made up of charges and payment transactions. The possible choices in transactiontype are:
Regular Charge
Late Charge
NOD Charge
Nod Late Charge
Insurance Charge
Other Charge
Regular Payment
Late Payment
NOD Payment
Nod Late Payment
Insurance Payment
Other Payment

The code below works great to ask the user to make a selection and then returns the correct data for me to use in my mergefileprint() however after playing with it I realized that the only choices the user should have on the popup selection should be charges. (it would be silly to remind them to pay a payment)

I have tried numerous methods to restrict the selection to only charges but I guess I do not have a good enough grasp on the workings of @FormFieldValue() and AppendStringArray() (at least this is the section I thought I need to modify)

Any suggestions on what or how I need to change this code?  Thanks




var n as Int
var vCount as Int
var vEdits as String
var vChoice as String

var vbilledAmount as String
var vtransactionId as String
var vChargememo as String




If @Mode() < 2
     {
           
vCount = @FormResultSetTotal("Payments")

     If vCount = 1 Then


                 If @FormFieldValue("Payments", "transactionType", 1) = "" Then
                 vCount = 0

                 For n = 1 to vCount


                 vEdits = @AppendStringArray(vEdits, "Print Reminder for Transaction# " + n)
//writeln(vedits)
                 Next

                 PopupSelectPosition(4, @XPos(ThisElement), @YPos(ThisElement))
                 vChoice = @PopupMenu("" + vEdits + ";"  ,"choose to print")
           
                 
                 
                 TempTransType = @FormFieldVAlue("payments", "Transactiontype", @Num(vChoice))
                 vbilledAmount = @FormFieldVAlue("payments", "billed Amount", @Num(vChoice))
                 vtransactionId = @FormFieldVAlue("payments", "TransactionId", @Num(vChoice))
                 //vChargememo = @FormFieldVAlue("payments", "ChargeMemo", @Num(vChoice))
                       
                 //This is were my MergeFilePrint code will go
                 writeln(TempTransType)
                 writeln(vbilledAmount)
                 writeln(vtransactionId)

}

Carl,

Thank You, Thank You, Thank you, Thank you.

Your code was great, I just had to understand @Instr() and modify it to my subform name. after that it was perfect!

         If @Instr( @FormFieldValue("payments", "TransactionType", n), "Charge" ) > 0
                vEdits = @AppendStringArray(vEdits, "Print Reminder for Transaction# " + n)

Thanks again, I will surely utilize what I learned from you, over and over again.