Hi Sean,
yup it is. I wasn't expecting things to be smooth even if I did know oracle for the migration. It's handy that there is alot of support if you get stuck on using it.
One follow up question: as I mentioned before, the procedure is to process MS Access reports because of how slow JET takes to generate them (some tables have 7k records). How would I create the report once I've finished the procedure? I suppose its going to be a VBA coding job after I provide the execute reports([parameters]) for the View Report button but would like to know exactly what I need to do after the procedure is done.
Regards,
Ben
On 8/17/06, Sean Davis <sdavis2@mail.nih.gov> wrote:
On 8/17/06 8:42 AM, "ben sewell" <mosherben@gmail.com > wrote:
> Hi Sean,
> after some debugging of the error messages I managed to create the function
> without any errors. For the record type being returned, it is dependent on
> the report_id so I'll have to add the user defined type in the front end
> where I execute the procedure.
>
> Anyways, I've attached the working script for anyone who is curious to see
> what had to be sorted out. Now I just need to finish off the select
> statement in the first if and then finish it for the other 4 if's. :)
Ben,
Great to hear you got it working. Postgresql is pretty cool, eh?
Sean
