Search found 5 matches

by [email protected]
Thu Oct 18, 2018 6:49 pm
Forum: Custom Reports
Topic: Exporting to MDB
Replies: 10
Views: 71676

Re: Exporting to MDB

Yes, I believe I am. The part I find confusing is that this year we've had just over 40 Sundays so far. Of those Sundays 16 don't show any Activity data entries for the ATDATA table in Access. I have now found each one of those missing entries by reversing the month and the day while searching in t...
by [email protected]
Thu Oct 18, 2018 12:57 pm
Forum: Custom Reports
Topic: Exporting to MDB
Replies: 10
Views: 71676

Re: Exporting to MDB

Yes, I believe I am. The part I find confusing is that this year we've had just over 40 Sundays so far. Of those Sundays 16 don't show any Activity data entries for the ATDATA table in Access. I have now found each one of those missing entries by reversing the month and the day while searching in t...
by [email protected]
Wed Oct 17, 2018 4:35 pm
Forum: Custom Reports
Topic: Exporting to MDB
Replies: 10
Views: 71676

Re: Exporting to MDB

Thank you for your quick reply. I am not at all familiar with Foxpro, so I will need some pointers to inspect the tables themselves. Our Power Church application is located on a network at our church. Dates in our Power Church Plus application are formatted as mm/dd/yyyy. The PC we are working with...
by [email protected]
Tue Oct 16, 2018 11:45 pm
Forum: Custom Reports
Topic: Exporting to MDB
Replies: 10
Views: 71676

Re: Exporting to MDB

OK, thanks for pointing this out. The export was handling the field type properly and handling the data properly, but the "auto" designation in Access was coming in by default and getting rid of everything after the decimal. We just needed to define the "scale" in the create table's field definitio...
by [email protected]
Sat Oct 13, 2018 11:43 am
Forum: Custom Reports
Topic: Exporting to MDB
Replies: 10
Views: 71676

Re: Exporting to MDB

OK, thanks for pointing this out. The export was handling the field type properly and handling the data properly, but the "auto" designation in Access was coming in by default and getting rid of everything after the decimal. We just needed to define the "scale" in the create table's field definitio...