Hello

I’ve got a couple of questions and scenarios.

Coming from a QA database the previous method for keeping track of payment history was done using 80 fields! D1 – D40 was used to keep track of payment dates A1 –A40 was using to store payment amounts. I’m guessing this was accomplished using a QA post method because I can’t find any programming to figure out how they did it.

I created a form and linked it to the main database that allows them to enter all the payment details. If I wanted to keep the current system how would I know which empty D and A fields were next to post to? From  your previous help I know how to loop through one field but how do I do 80 separate?! Also, some records have already reached the D40 and A40 fields. In the current database this data is then ONLY written to the fields dumdate and dumamt. Thus, payment history stops after D40 and A40 and only the last date and amount is kept. Not so good, I know. There has to be a better way, right?

I was looking at sample programs (such as the seasons example db in Sesame) and I thought I could greatly improve the payment history by mimicking an invoice form setup. Does this seem like good idea? Do you have any other suggestions? If not, my question is this. Do I create a new database or use the existing? Payment history has only eight fields. In either case how to I create a new history that is linked to the original account? I’m using sesame 2.03.

Still having a blast with Designer! Any help or suggestions are greatly welcomed
Thanks,
Rob

Woo Hoo! Yes, the fields are named d1, d2, a1, a2, etc

Thank you!

Thanks for the help!

If @IsBlank(@Field("D" + @Str(vLoop)))

Can I use this to look through another form as well? I'm getting errors, errors, and more errors, when I try  to add a form name.

Also, thanks for the subform pointer. I'm RTFM'n and creating a new database as we speak

I have created my two databases (costs, payhistory). I created my subforms and linked them. It looks great thanks for the tip. For all practical purposes costs and payment act the same.

My question is this. On the parent form I'm calling some fields from the main database (qamain), after they choose payment methods, amount, ect, I would like to update the qamain and write a brand new record to the subform database using some kind of button

I created a button on the parent form hoping it would create a new record but it's not working.

var nn as Int

	nn = @FormNewRecord("payhistory")
	FormFieldValue("account no:", "payment date:", "method:", "check no:") 

Could you point me in the right direction?
Thanks!!

I'm reading, I'm reading This stuff seems like Greek to me. If you couldn't tell, I'm a hardware guy. I've looked at all the samples but none of them seem to do what I'm trying to accomplish Once I'm done with this program I have ten more! (JOKING)

It works great if the button is within the subform. How would/could I do this with the button on the main form? Also, I've looked at programming examples on creating a new unique field when creating a new record, would this apply to me? When I create a new record manually it seems to work fine. Thoughts?

You're amazing, I'm thinking about naming my first born after you