>Hi, Dawa...
>
>First thing that comes to mind - create separate projects for your business logic and your data access. While some projects tend to combine the two in some way, I've come to realize the value of keeping the two separate.
>
>Any reason you're using VFP as your tool for querying and reporting? If you've worked out the mechanics of it and have chosen to proceed that way, fine - but depending on the types of reports you're building, the combination of stored procs in your back-end and Crystal may offer some advantages. (Again, depending on the details).
Kevin,
Thank you for the reply!
>First thing that comes to mind - create separate projects for your business logic and your data access. While some projects tend to combine the two in some way, I've come to realize the value of keeping the two separate.
Could you explain further? In this instance, what is involved in the data access?
>Any reason you're using VFP as your tool for querying and reporting?
I am considering VFP for reporting because I hear Crystal Reporting costs to distribute and we would like to cut as much cost as possible for our clients. Besides we have learning curve with Crystal.
Dawa Tsering
"Do not let any unwholesome talk come out of your mouths,
but only what is helpful for building others up according to their needs,
that it may benefit those who listen."
- Ephesians 4:29-30 NIV
Dare to Question -- Care to Answer
Time is like water in a sponge, as long as you are willing you can always squeeze some.
--Lu Xun, Father of Modern Chinese Literature
