Re: Off Topic - Access to Postgres

On 28 Dec 2005 03:37:26 -0800, "Hank" <hankrunner@xxxxxxx> wrote:

>
>Steve Jorgensen wrote:
>> On 27 Dec 2005 18:00:46 -0800, "Hank" <hankrunner@xxxxxxx> wrote:
>>
>> > We have just recently migrated the data from our Access 2000
>> >backend to Postgres. All forms and reports seem to run correctly but,
>> >in many cases, very slowly. We do not want to switch over until we
>> >can speed things up. We would like to start implementing Stored
>> >Procedures so we can do Server-Side processing.
>> > Can anyone recommend a book that would help us learn how to
>> >use sprocs or pass-through queries? I apologize if my terminology is
>> >incorrect. I am in the position of not quite knowing how to ask the
>> >right questions.
>> >Thanks,
>> >Hank Reed
>>
>> When you have a speed problem with client/server, using pass-through queries
>> and stored procedures is not usually the best answer, and may not help at all.
>> Doing that is, however, a good way to make your program 4 or 5 times harder to
>> develop and maintain.
>>
>Steve,
> Thanks for the advice. I have always used PKs in every
>table. My novice understanding of a database like Postgres is that we
>would ONLY get the filtered records. I have been led to believe (or
>convinced myself) that a stored procedure would select and return only
>the records of interest, thus saving bandwidth and transfer time, in
>general. If sprocs and pass through queries are not the solution then
>what would you recomend?
>Thanks again,
>Hank Reed

All you need is to make sure you use queries to aggregate and-or filter your
results. In some cases, a query may fail to optimize well and pass the SQL
correctly to the back-end for processing, and then you may have to tweak it to
get it right, or you may even have to create a server-side view, but as soon
as you use an SP, you're opening a can of worms, so use that as a last resort.

Note that using form filtering is -NOT- the same as using a query for
filtering, and does not cause the filtering to be done by the server as query
would.
.

Relevant Pages

  • Re: Help with Microsoft help on linking Access to Outlook
    ... Tools - references - tick Microsoft Outlook object library. ... in the criteria cell in the graphical query builder. ... the same filtered recordset every time. ... normal form to allow the normal filtering process and viewing of the ...
    (microsoft.public.access.formscoding)
  • Re: Help with Microsoft help on linking Access to Outlook
    ... in the criteria cell in the graphical query builder. ... use as the source in the routine. ... the same filtered recordset every time. ... normal form to allow the normal filtering process and viewing of the ...
    (microsoft.public.access.formscoding)
  • Re: Help with Microsoft help on linking Access to Outlook
    ... in the criteria cell in the graphical query builder. ... use as the source in the routine. ... the same filtered recordset every time. ... normal form to allow the normal filtering process and viewing of the ...
    (microsoft.public.access.formscoding)
  • Re: Help with Microsoft help on linking Access to Outlook
    ... Dim objOutlook As Outlook.Application ... in the criteria cell in the graphical query builder. ... the same filtered recordset every time. ... normal form to allow the normal filtering process and viewing of the ...
    (microsoft.public.access.formscoding)
  • Re: Help with Microsoft help on linking Access to Outlook
    ... Dim objOutlook As Outlook.Application ... in the criteria cell in the graphical query builder. ... the same filtered recordset every time. ... normal form to allow the normal filtering process and viewing of the ...
    (microsoft.public.access.formscoding)
Loading