William wrote:
1) Payroll apps require large tax libraries (federal, every state and
locality).
Split them into more files (diffrent states etc.) and include_once them
when they are needed,
and perhaps mysql can take part of the job.
4)Loosely Typed Variables.
I fear it might be to
The admin users will need to run long processes that take about
5-15 minutes each. They cannot timeout and they must be done
throughout the day
while general users are working in the application as well. Is
there a big problem with this? What steps should I take to ensure
these
Beau Hartshorne wrote:
The admin users will need to run long processes that take about
5-15 minutes each. They cannot timeout and they must be done
throughout the day
while general users are working in the application as well. Is
there a big problem with this? What steps
I don't know if this is possible, but in VB (I'd like to find something
similar in php) I would open a record set, and then filter / unfilter it for
similar issues (in a loop). I'm assuming you could use a similar approach
somehow in php.
Robert Cummings [EMAIL PROTECTED] wrote in message
Jeff Bluemel wrote:
I don't know if this is possible, but in VB (I'd like to find something
similar in php) I would open a record set, and then filter / unfilter it for
similar issues (in a loop). I'm assuming you could use a similar approach
somehow in php.
Sounds like a DB issue. Select
I don't know if this is possible, but in VB (I'd like to find
something
similar in php) I would open a record set, and then filter / unfilter
it
for
similar issues (in a loop). I'm assuming you could use a similar
approach
somehow in php.
Seems like a waste of resources. Why not do the
I am interested in writing a large scale, cross platform payroll/hr/gl appl
entirely in php + mysql Innodb (for transaction support).
I have 2 php programmers 1 asp/foxpro/access programmer to help me.
I see 4 big hurdles to overcome in my php design: Large Libraries, Long
Processes,
1. Never had any problems with big includes before.
2. Maybe add a console based prog which sits in the background and
process's jobs if you don't want to leave the web page open while
it works, etc.
3. Make them PDF's (pdflib), we use it, and once you get programming
in it, it's fairly easy.
4.
3)Reporting.
I think I can get by with HTML reports for the most part. however checks
and tax forms require precisely positioned reporting abilities.
I think that I will be better off using an external reporting
application (crystal,access,FoxPro etc) to generate these reports. But if
1) Large Includes
200K of includes? Piece of cake! Remember, it is the server that is doing
all of the work, not your clients. The issue is how many requests can your
server simultaneously process and is there enough overhead to do it. With
respect to speed, your server will cache the files
10 matches
Mail list logo
