RE: [INTERFACES] PostODBC/MS ADO
От | Dave Page |
---|---|
Тема | RE: [INTERFACES] PostODBC/MS ADO |
Дата | |
Msg-id | 000101be1c83$2d3b3120$2801a8c0@pc81.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Re: [INTERFACES] PostODBC/MS ADO (Byron Nikolaidis <byronn@insightdist.com>) |
Список | pgsql-interfaces |
> -----Original Message----- > From: owner-pgsql-interfaces@postgreSQL.org > [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Byron > Nikolaidis > Sent: 30 November 1998 15:42 > To: Dave Page > Cc: pgsql-interfaces@postgreSQL.org > Subject: Re: [INTERFACES] PostODBC/MS ADO > Yes, there are several areas the driver does not support. > However, I have been in the > middle of *EXTENSIVE* additions to the driver. These > include, Multi row-wise and <SNIP> Thats great, hopefully it will solve my problems. > I felt the same way at first. But it is useful, because even > in Windows, applications were > writing all over each other's log files. If you sort by date > in Explorer and do a refresh > before you look at the log files, the latest one will be > right at the top of the list. I > don't know if that is useful to you or not. Unfortunately, if I'm doing a long debugging session in the VB IDE, I quite often find that during the session I've used things like pgAdmin and dbManager (manages system parameters etc for our in house software) a couple of times so the log for the session running in the debugger ends up in the middle of the list somewhere as it's no longer the latest. This is mainly because VB has the useful feature of being able to stop, start, debug AND rewrite code whilst it is running which of course most other development packages can't do :-( I can see both sides to this argument and can live with it if it's a problem... Regards, Dave.
В списке pgsql-interfaces по дате отправления: