Bob,
I haven't tested it. Is this the Sybase "standalone" product?
Jeff
> -Original Message-
> From: Bob X [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 05, 2003 6:28 PM
> To: [EMAIL PROTECTED]
> Subject: SQL Server Anywhere and ODBC
>
>
> Does anyone use ODBC to connect to SSA?
Does anyone use ODBC to connect to SSA? I am on 5.8 and Windows XP.
Bob
I'm posting this on the off-chance that Stefan also reads this list.
I received an almost anonymous bug report from "Guest via RT
<[EMAIL PROTECTED]>", of which the closing lines said
"Module: DBD-Informix-2003.03.0401. I hope this will help you find
this bug and fix it. Sincerely yours Stefan".
The problem here is whose system variables? (IE the system the database
is designed on or where it will eventually live or where it will live
once its original host dies etc. .). Since you can't always control all
of these variables I have found that when I HAVE to use access that
things are more
On Wed, Mar 05, 2003 at 01:38:58PM -0500, Jeff Thies wrote:
>
>
> Tim Bunce wrote:
> >
> > On Wed, Mar 05, 2003 at 02:36:50PM +, Volker I. Lipper wrote:
> > > Hi Jeff,
> > >
> > > the correct syntax in access itself would be:
> > >
> > > >#9/30/1999#
> > >
> > > the writing of the data (mm.d
Tim Bunce wrote:
>
> On Wed, Mar 05, 2003 at 02:36:50PM +, Volker I. Lipper wrote:
> > Hi Jeff,
> >
> > the correct syntax in access itself would be:
> >
> > >#9/30/1999#
> >
> > the writing of the data (mm.dd or dd.mm or mm/dd) belongs to the
> > system variables set on the system acess is
Heres the problem
$sth->execute(my $name);
You RE-initalizing the $name in the execute. Get rid of the my and it
should work.
You may also want to make sure case restrictions are not a problem (ADAm !=
adam);
Adam
-Original Message-
From: Tony Bandy [mailto:[EMAIL PROTECTED]
Sent: We
Hello everyone,
Please forgive in advance if this has already been posted...fairly new
to the list...just subscribed.
If you have a minute, any ideas? I would be most grateful.
I'm running apache 2.0x with mod_perl on a windows 2000 server.
I have a form page on the website where folks can e
From: "Jenda Krynicky" <[EMAIL PROTECTED]>
>
> I'm afraid you are out of luck with Perl 5.6.1. You'll have to
> upgrade to Perl 5.8 t get this working.
>
> I do use the multithreading with Perl 5.6.1 under Win32 and do use
> DBD::ODBC to get data from the database, but I only use DBI+DBD::ODBC
> in
On Wed, Mar 05, 2003 at 02:36:50PM +, Volker I. Lipper wrote:
> Hi Jeff,
>
> the correct syntax in access itself would be:
>
> >#9/30/1999#
>
> the writing of the data (mm.dd or dd.mm or mm/dd) belongs to the
> system variables set on the system acess is installed on. But in
> every case y
I have a very long running Perl process. I recently upgraded the
DBI from 1.32 to 1.33 (and then 1.34) and now, the process is leaking
memory. Given the complexity of the project, it's not possible to
reduce it to a simple test case at this time, but it's definitely
related to the DBI -- if I dow
Hi Jeff,
the correct syntax in access itself would be:
>#9/30/1999#
the writing of the data (mm.dd or dd.mm or mm/dd) belongs to the
system variables set on the system acess is installed on. But in
every case you have to use the # sign.
hth
Li
> Date: Wed, 05 Mar 2003 07:24:04 -050
"Tim Bunce" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Ah, okay. Sorry. Edit the lib/DBD/Proxy.pm file and change the $this in
the
> line that's causing the error, to be $dbh.
>
Done and done! : )
I'm having trouble with date time in Access with DBI/ODBC
I'm trying to do this:
SELECT * FROM some_table WHERE date_time_field > 11/30/99
That's giving me all dates, where:
SELECT * FROM some_table WHERE date_time_field < 11/30/99
Is giving me none.
I must have done something completely wron
From: "Dean Arnold" <[EMAIL PROTECTED]>
> While trying to test some multiprocessing on Win2K (ActiveState 633),
> I ran into an issue I'm hoping you can shed some light on. If I open a
> $dbh before forking off some kids that also open some $dbh's, I get
> the following error in the kids:
>
> "DBD
On Tue, Mar 04, 2003 at 10:58:22PM -0500, Jeff Thies wrote:
> I have an Access database with funny field names like: REPORT #
>
> I forgot the advice to use square brackets [] and used double quotes
> instead : "REPORT #".
>
> Now, that works fine. But is that going to cause me trouble
> somew
On Tue, Mar 04, 2003 at 04:21:10PM -0800, Dean Arnold wrote:
> > On Tue, Mar 04, 2003 at 02:31:37PM -0800, Dean Arnold wrote:
> > > While trying to test some multiprocessing on Win2K (ActiveState 633), I
> ran
> > > into
> > > an issue I'm hoping you can shed some light on. If I open a $dbh before
17 matches
Mail list logo