Assign check number & save.

[Art123]

I am working on an application that, in part, issues a check. Using Group Header, Detail (sub report), Page footer (check in the Page Footer). Most will have multiple entries on the check stub (detail subreport). My problem is how to assign the check number, and make it a matter of record, so that it can be used later to balance the bank account, etc. I do not know Xbasic.
Can you give me any ideas?

[MikeC]

Re: Assign check number & save.

Arthur,
I am not completely understanding how you are attempting to do this. It sounds like you are using a report as your use of terms implies, but then you want the report to be used to enter data somehow?? Reports are used to show data, not enter it into a table....a form or browse is used for data entry.

[Keith Hubert]

Re: Assign check number & save.

Hi Arthur,

Welcome to Alpha.

It is a shame that you'r starting with V8 when V9 is available at a give away price and it has such nice features to work with.

Given that,

My problem is how to assign the check number

have you looked at autoincrement in field rules?

[Mike Wilson]

Re: Assign check number & save.

Aurthur,
Welcome to Alpha!

I am with MikeC on this. The terms you are using are terms for a Report. A report collects and presents record values that exist in the records in (a) table(s). Record values are entered through forms and browses (and xbasic). It is in the entering of record values where the 'check number" would become a value in a field in the table for the report to present. Are you clear on this?

Keith,
A new look for you... nice.

[Peter.Greulich]

Re: Assign check number & save.

As Keith said, you would probably use an autoincement field for the check no. Your check data gets created on a form, then you print your check (as a report).

[Art123]

Re: Assign check number & save.

Let me change the wording:
Say you have a table with three entries ID#25 $5.00; ID#30 $7.00;
ID#30 $2.00. You have one #25 and two #30. An autoincrement field would assign a check number to each individual entry. (3 numbers) But you would only produce two checks because the two #30 would be grouped and combined. An autoincrement field would work fine if there were only one entry for each ID# (a check issued for each one). But when the program combines (in the report) two or more items, then the autoincrement field wouldn't work. I'm missing something here, in basic design maybe?

[Peter.Greulich]

Re: Assign check number & save.

I'm missing something here, in basic design maybe?

I think we are all a little confused. What tables do you have and what do they do?

[MikeC]

Re: Assign check number & save.

Arthur,
Your two records of ID#30 would be children of a parent table it sounds like. The parent would be auto-incremented and in that way the auto-increment would have generated the ID# of 30.

That's the way I see it. IOW you would have the parent field that is auto-incremented and then a corresponding child field that houses the auto-incremented data (but is not incremented)---this creates the linkage between the parent and child.

[robert]

Re: Assign check number & save.

why would a report combine two records into one? The autoincrement field is separate from the ID# field (as I understand it). If the autoincrement field is on the report, you will get a separate page for each record (assuming you page break on the autoincrement field).

[Tom Cone Jr]

Re: Assign check number & save.

Robert, I think Mike is suggesting that the data structure for a check could consist of two linked tables, rather than just one. In the same way an Invoice data structure often consists of two tables. Imagine a check written to a vendor to pay multiple bills. The chk_Hdr table could contain fields describing the check itself (date, amount, payee, and chk_number). A child table, linked one to many, could contain fields describing the bills being paid... in this child table structure there would be a foreign key field linking each record to the chk_hdr record. I do this sort of think in QuickBooks when I pay a visa bill. Perhaps you have seen something similar?