ginerjm

So you're basically writing a transfer mechanism to take a file from someone who puts on the server and you want it on a client. What about an email with an attachment that you process using a script that handles that inbox?

copied from the server pc to the folder - on what? What folder on what device are you talking about. If this item is being placed onto the server for you to then download to the client - yes you will have to execute the script on the client somehow. OTOH - if it is on the server just waiting to be processed by something, why not schedule a cron job to run on the server every x minutes to actually do that process? You could then do something on the client that does a check of what results have been produced.

And why do you want to get into this? You don't code. Suddenly you want to run some code? Why?

CAn you alter the char set on an ipad?

Probably a different character set. YOu may need to do a type conversion for all the input from the ipad if it doesn't match your db set.

PS - using addslashes is hard to verify since they don't show up visually. If you are doing this to add to a db go ahead and do it and then see if the data is completely returned in a query result.

If you read the manual you'll see that you need to supply a result argument for the changed string.

What didn't addslashes do? Please elaborate since "wasn't working" doesn't say shit. And as for using str_replace - is that your EXACT code?

You could use str_replace I suppose. Test it out. That's what I would have done before writing here. And what is wrong with addslashes? What is it NOT doing?

Curious question. Why do you have a field named "Oracleid"? Is this an oracle db? Do you work with Oracle people? Do you work for Oracle? For an id-type field a size of 150 chars seems rather large. Why so big? It's just an id, a key, a lookup value or user number or record number, isn't it? Do people have to remember their Oracleid? Why the field named 'theday'? What day is it. The day you created the record? Today? A day related to one of the six time fields you have stored? You should name it so that one knows what it represents at the very least. Not "theday". OR MORE you should not have it at all. You have all these time/timestamp fields which represent values that can easily produce the day from their values, so do that instead. Reason. 500 chars? Is this a free-form text field that describes something that can be read only? You can't use it to categorize any kind of actions among all of your people. That would require some kind of code that helped to identify various types of "reasons". Is that what you are trying to do by even recording a "reason" field? Fullday. Looks like a good place for a boolean-type field. Why a tinyint? Same for "isdone". And why would you remove the records for former employees? You would be losing valuable data that might come in handy for research or for answering questions about former employees. Why not just add a status code to the table with a lookup table to define the different codes you may have. When someone departs, you mark them "gone" or "retired" or "inactive" or "fired", etc. If these are truly employees does your government not require you to keep their records for a number of years?

Have you ever written reports before?? For that matter - have you ever read a report? What you are showing looks like no other report I have ever seen. Really???

And if you search the php manual for that function name what do you find? Doesn't show up in mine. Is this some package that has to be specifically included into your php install?

And that hopefully has been corrected so as not to do that html output?

Can you show us some of your fpdf code? Just a sample of 20-30 lines from one of your routines that generates the pdf file? Just want to make sure of something since I'm still trying to help you.

Well - that's the problem as the messages tell you. Can't help you out - not familiar with any of this particular task.

So he can't find whatever COM is. Is it a class? Is the class being loaded by any require or include? The errror reporting code is essential for picking up errors during the coding mode. Turn them off before putting into production.

And line 6?

And WHAT IS that message? That's what I was asking you. You don't need an IDE to read a message in your browser. Or - if the functions themselves capture the messages the documentation for them should tell you how to display them during execution.

FWIW - When I use FPDF I usually want the pdf document to just show up on a clean page of my web browser I use $pdf->Output(); That's all it takes.

Assuming that you have written the code correctly and not made any typos, what is the problem with it? You aren't having success - so are there any messages coming back? For you to say it doesn't work sure can't help us to see what's wrong, assuming that it is written correctly.

Again - let me try Your query will build a result set of all the data you need to report on. As you fetch each row (assuming mutiple ones for each person being reported) you will gather the data and use it to write out pieces of your pdf document. Read another row and build some more pdf output. When you recognize the need to end the first page do your addpage call and continue on with person until the second page is done. That will be noticed when the next fetch has a new userid key telling you to start the next person. Close out the current page that you just finished, reset the page number and start the new page (basically just an add page call with perhaps new headings). Hopefully you wrote your FPDF logic to simply write out your well-designed page using a set of data. You need to see that set of FPDF logic as the way to generate a report. Wrap that in something so that you can loop thru the query results, get all the data you need for the FPDF process and call it. This isn't rocket science. It just needs the proper design to collect data and to make the necessary FPDF function calls and a bit of php to recognize when a new page needs to be added and to recognize the start of a new person's data. (Please don't re-post this)

I"ll try and contribute again and hope to get my point across. Write your query to select all of the people you want to report out. When you finally run that query, pass the results variable to your fpdf code script. Begin a loop there on those results that does the fetch for each record and let your fpdf code process it. When you loop finishes - close out your fpdf and send it to the client. Remember you CANNOT SEND ANYTHING TO THE CLIENT EXCEPT THIS CLOSED FPDF CONTENT. That's why you use two scripts - one to collect any arguments and do the query and report back any errors and the other to take the set of data and generate the fpdf output and actually do the outputting to the client. Whew! (Please don't re-post this post. Read it, digest it and go do the work.)

Good luck. You are beyond my ability to help you. You seem to be a bit short on the education of how to program, read manuals, or experiment.

Hundreds of records should not be a concern. Hint? No - you need to learn how to spec things out and then examine them. Enjoy!

I"m going to let you think this out. I'm going to assume that you wrote a report that shows one person's data. So now you simply expand the query to generate multiple rows of data and use that in a loop to output each record on the pdf. Make sense? So look at YOUR code and do some re-thinking. As I said earlier - if you simply want to generate a person's data as one page of a report then add a page break after doing one guy and let the loop do all the work. It's all about doing your design homework before you sit down and begin coding. And please don't re-post this when you make your next post. Such a waste.