Re: ODBC with Visio - what's wrong with my connection string?

Thanks - unfortunately adding the backslash does not work and I'm fairly
sure that I can't rename the visio custom property from Prop.whatever to
Prop_whatever. That would be ideal.

Does anyone have any other suggestions about connecting Visio to
PostgreSQL?

Corey Gibbs wrote:
>
> Good Evening Steve,
> Yeah PG is complaining about the .'s because it is used in floating point
> constants and to seperate table and column names...
> i've never come across this, but you *might* try escaping it with a
> backslash \.
> or you could try putting it into a table called Prop, or if hte prop part
> isn't important, you could convert it to Prop_
> that's all i can think of
> corey
>
> ----- Original Message -----
> From: "Tulk Steve" <tulk_steve(at)bah(dot)com>
> To: <pgsql-odbc(at)postgresql(dot)org>
> Sent: Tuesday, August 20, 2002 1:45 PM
> Subject: [ODBC] ODBC with Visio - what's wrong with my connection string?
>
> > I'm attempting to link VISIO shapes to my PostgreSQL database. I'm
> > linking the properties of the shape to columns in a view. Visio sends
> > an ODBC request, but all that is returned is:
> >
> > parser error at or near "."
> >
> > Here is what visio is sending to map the requests to the properties of
> > the Visio shape:
> >
> >
> ="ODBCDataSource=PostgreSQL-csc2426|ODBCQualifier=ODBCDataSource=PostgreSQL-
> csc2426|ODBCTable=roadmapview|3|activityid=Prop.activityid|acode=Prop.acode|
> ccode=Prop.ccode|57|actor1=Prop.actor1=0|actor10=Prop.actor10=0|actor2=Prop.
> actor2=0|actor3=Prop.actor3=0|actor4=Prop.actor4=0|actor5=Prop.actor5=0|acto
> r6=Prop.actor6=0|actor7=Prop.actor7=0|actor8=Prop.actor8=0|actor9=Prop.actor
> 9=0|aname=Prop.aname=0|as1=Prop.as1=0|as2=Prop.as2=0|as3=Prop.as3=0|as4=Prop
> .as4=0|as5=Prop.as5=0|cname=Prop.cname=0|functionalrole1=Prop.functionalrole
> 1=0|functionalrole10=Prop.functionalrole10=0|functionalrole2=Prop.functional
> role2=0|functionalrole3=Prop.functionalrole3=0|functionalrole4=Prop.function
> alrole4=0|functionalrole5=Prop.functionalrole5=0|functionalrole6=Prop.functi
> onalrole6=0|functionalrole7=Prop.functionalrole7=0|functionalrole8=Prop.func
> tionalrole8=0|functionalrole9=Prop.functionalrole9=0|ots1=Prop.ots1=0|ots10=
> Prop.ots10=0|ots2=Prop.ots2=0|ots3=Prop.ots3=0|ots4=Prop.ots4=0|ots5=Prop.ot
> s!
> >
> 5=0|ots6=Prop.ots6=0|ots7=Prop.ots7=0|ots8=Prop.ots8=0|ots9=Prop.ots9=0|post
> 1=Prop.post1=0|post10=Prop.post10=0|post2=Prop.post2=0|post3=Prop.post3=0|po
> st4=Prop.post4=0|post5=Prop.post5=0|post6=Prop.post6=0|post7=Prop.post7=0|po
> st8=Prop.post8=0|post9=Prop.post9=0|pre1=Prop.pre1=0|pre10=Prop.pre10=0|pre2
> =Prop.pre2=0|pre3=Prop.pre3=0|pre4=Prop.pre4=0|pre5=Prop.pre5=0|pre6=Prop.pr
> e6=0|pre7=Prop.pre7=0|pre8=Prop.pre8=0|pre9=Prop.pre9=0|"
> >
> > Obviously PostgreSQL doesn't like the .'s. I'm fairly sure I won't be
> > able to change the formatting of the properties in Visio to eliminate
> > the .'s - any ideas on how the request can be sent witout PostgreSQL
> > complaining?
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org