R
Robert G Randall
I have two problems...
I have a software package for wineries that I have had for about 11 years.
The first program I never had any problems.
As the program and the user base grew, I needed to add a Point Of Sale
interface, which is much more complicated than the original invoice. Along
the way the application began crashing. It was always during a change that
cause the intire form to recalculate. I minimized the problem by not haveing
some of the fields recalcualte except on demand - meaning I added a button
which did the form calculations on request and not when the form(s) were
recalculating. This seemed to make the crashing less frequent but did not
solve my problem.
Due to changes in WA state sales tax collection I am re-writting my
application from basically ground zero. It has been going along great, but I
am again experience crashing. It always happens when I have selected
something in a drop down box that cause the form to requery, but it is never
consistant as to when it will happen.
The Main form is frmInvoice then there are several subforms
frmInvoice02Detail, frmInvoice03DretailPay, frmInvoiceButtons
The Main form has several tables attached to it that pull in codes for
taxing, the type of sale, shipping etc..
I am not a great VB code person - I am learning a lot but I do most of my
work using the tools in MS Access, that is why I use the software. So I use
a lot of queries with the tables needed to do the functions required.
What I am wondering is - would I be better off to use SQL functions for
pulling the items like the tax code information, the shipping information
etc... would this stop my form from trying to requery and maybe stop my
crashing.
It is a complex form - there is a lot of information gathing required in
order to do all the unbelieveable amount of reporing required by the
different states.
Any adivce would be greatly appreciated.
Thanks
I have a software package for wineries that I have had for about 11 years.
The first program I never had any problems.
As the program and the user base grew, I needed to add a Point Of Sale
interface, which is much more complicated than the original invoice. Along
the way the application began crashing. It was always during a change that
cause the intire form to recalculate. I minimized the problem by not haveing
some of the fields recalcualte except on demand - meaning I added a button
which did the form calculations on request and not when the form(s) were
recalculating. This seemed to make the crashing less frequent but did not
solve my problem.
Due to changes in WA state sales tax collection I am re-writting my
application from basically ground zero. It has been going along great, but I
am again experience crashing. It always happens when I have selected
something in a drop down box that cause the form to requery, but it is never
consistant as to when it will happen.
The Main form is frmInvoice then there are several subforms
frmInvoice02Detail, frmInvoice03DretailPay, frmInvoiceButtons
The Main form has several tables attached to it that pull in codes for
taxing, the type of sale, shipping etc..
I am not a great VB code person - I am learning a lot but I do most of my
work using the tools in MS Access, that is why I use the software. So I use
a lot of queries with the tables needed to do the functions required.
What I am wondering is - would I be better off to use SQL functions for
pulling the items like the tax code information, the shipping information
etc... would this stop my form from trying to requery and maybe stop my
crashing.
It is a complex form - there is a lot of information gathing required in
order to do all the unbelieveable amount of reporing required by the
different states.
Any adivce would be greatly appreciated.
Thanks