ODBC question Blank Title 59797

Yahoo Archive
1
 We use 'READ UNCOMMITTED ' for all of our 'read-only' special apps/reports, which is the majority of the time.
Â
 We have some special apps/ cases where 'READ COMMITTED' is used , where records can be created/updated/deleted. As everyone has said, extreme care should be taken in this scenario. We're 'updating' where we believe little harm can follow, such as 'auto-linking drawings/documents to partRevs', updating incorrect/missing ProdCodes in Parts, updating user fields, etc.
Â
 We have a new app that , thru a BAM, creates an New PO , PO Detaill, PO release when a new order is placed for a particular group of parts. Risky but so far, so good and we're not using ODBC at all in this case, strictly Progress 4GL.

--- On Wed, 1/6/10, Steven Gotschall <sgotschall@...> wrote:


From: Steven Gotschall <sgotschall@...>
Subject: Re: [Vantage] ODBC question
To: vantage@yahoogroups.com
Date: Wednesday, January 6, 2010, 4:49 PM


Â



READ UNCOMMITTED is read only. The other three allow you to write back to the database, but I don't know what the differences are. You can find descriptions of them on the Internet if you can make sense of them. Only use READ UNCOMMITTED on a live multiuser Progress database or else you will lock users out of tables and records, not to mention that fact that writing to your Progress through ODBC has to potential of corrupting your entire database.

____________ _________ _________ __
From: Keith Mailloux <keith.mailloux@ fergusonperf. com>
To: vantage@yahoogroups .com
Sent: Wed, January 6, 2010 4:28:44 PM
Subject: [Vantage] ODBC question

Â
I am looking for some insight into ODBC connection configurations.
Anyone know what the following Advanced Connection parameters mean?

READ COMMITTED, READ UNCOMMITTED, REAPEATABLE READ, and SERIALIZABLE

Thanks in advanced.

Keith

------------ --------- --------- ---
This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]











[Non-text portions of this message have been removed]
2
Hey everyone this is a pretty obscure quetion but I'm hoping somebody
has run across this before and can help.

I am using an ODBC connection to retrieve data from Vista/Vantage
8.03 and have run into a problem. I am trying to create a report of
the files attached to current jobs. I found the table that holds the
data but have found that when a record is over 80 characters long it
will not return anything but if I truncate the output to 80 character
it will work. For example:

SELECT
XFileAttch.Key1,
XFileAttch.Key2,
XFileAttch.AttachNum,
SUBSTR(XFileRef.XFileName,1,80) as FileName

But this will return nothing for the XFileName field when it
encounters a value greater than 80 character long:

SELECT
XFileAttch.Key1,
XFileAttch.Key2,
XFileAttch.AttachNum,
XFileRef.XFileName as FileName

As far as I can tell this has to do with the ODBC Driver but I'm not
positive. If anyone can help me with this one I'd appreciate it.

Michael Gensel,
Livonia Tool & Laser
936 Anderson Road
Litchfield, MI 49252
ISO 9001:2000 Registered
Email: michaelg@...
Website: www.livoniatool.com
Phone: 888-875-0833
Fax: 517-542-2427
3
> SELECT
> XFileAttch.Key1,
> XFileAttch.Key2,
> XFileAttch.AttachNum,
> SUBSTR(XFileRef.XFileName,1,80) as FileName

I think someone previously suggested something like:

SELECT
XFileAttch.Key1,
XFileAttch.Key2,
XFileAttch.AttachNum,
SUBSTR(XFileRef.XFileName,1,80) as FileName1,
SUBSTR(XFileRef.XFileName,81,80) as FileName2,
Etc.

And then concatenating the FileName# fields together.

Mark W.
4
I actually tried that but the driver returned the following error:

[DataDirect][ODBC OPENEDGE driver][OPENEDGE]Character string is too
long (8184) S1000

~ Mike

--- In vantage@yahoogroups.com, "Mark Wonsil" <mark_wonsil@...> wrote:
>
>
> > SELECT
> > XFileAttch.Key1,
> > XFileAttch.Key2,
> > XFileAttch.AttachNum,
> > SUBSTR(XFileRef.XFileName,1,80) as FileName
>
> I think someone previously suggested something like:
>
> SELECT
> XFileAttch.Key1,
> XFileAttch.Key2,
> XFileAttch.AttachNum,
> SUBSTR(XFileRef.XFileName,1,80) as FileName1,
> SUBSTR(XFileRef.XFileName,81,80) as FileName2,
> Etc.
>
> And then concatenating the FileName# fields together.
>
> Mark W.
>
5
While taking a look at progress's support page I think I may have
found what the problem is. It looks like there is an SQLWIDTH option
for the field that needs to be increased, but as far as I can tell
with Vista's version of OpenEdge you can make the change needed to
fix the problem in the data dictionary. So if anyone knows any other
workarounds I would appreciate to hear from you.

~ Mike Gensel

--- In vantage@yahoogroups.com, "megensel" <michaelg@...> wrote:
>
> I actually tried that but the driver returned the following error:
>
> [DataDirect][ODBC OPENEDGE driver][OPENEDGE]Character string is too
> long (8184) S1000
>
> ~ Mike
>
> --- In vantage@yahoogroups.com, "Mark Wonsil" <mark_wonsil@> wrote:
> >
> >
> > > SELECT
> > > XFileAttch.Key1,
> > > XFileAttch.Key2,
> > > XFileAttch.AttachNum,
> > > SUBSTR(XFileRef.XFileName,1,80) as FileName
> >
> > I think someone previously suggested something like:
> >
> > SELECT
> > XFileAttch.Key1,
> > XFileAttch.Key2,
> > XFileAttch.AttachNum,
> > SUBSTR(XFileRef.XFileName,1,80) as FileName1,
> > SUBSTR(XFileRef.XFileName,81,80) as FileName2,
> > Etc.
> >
> > And then concatenating the FileName# fields together.
> >
> > Mark W.
> >
>
6
The openedge driver's server side process app likely is the cause (not set up properly to handle that particular table column's 80+ characters).

An (ugly) work around might be to return a calculated column "TRIM(table.column)" to potentially compress the returned deta below the 80 character limit.

I've forgotten the SQL keywords but you could also return multiple calculated columns that bring back the LEFT and RIGHT halves of the oversized column data seperately. You would then need to rejoin them in your report tool (example for excel: Cell formula = concatenate(Left truncated returned cell data row/column, right truncated returned cell data row/column)).





megensel <michaelg@...> wrote:
Hey everyone this is a pretty obscure quetion but I'm hoping somebody
has run across this before and can help.

I am using an ODBC connection to retrieve data from Vista/Vantage
8.03 and have run into a problem. I am trying to create a report of
the files attached to current jobs. I found the table that holds the
data but have found that when a record is over 80 characters long it
will not return anything but if I truncate the output to 80 character
it will work. For example:

SELECT
XFileAttch.Key1,
XFileAttch.Key2,
XFileAttch.AttachNum,
SUBSTR(XFileRef.XFileName,1,80) as FileName

But this will return nothing for the XFileName field when it
encounters a value greater than 80 character long:

SELECT
XFileAttch.Key1,
XFileAttch.Key2,
XFileAttch.AttachNum,
XFileRef.XFileName as FileName

As far as I can tell this has to do with the ODBC Driver but I'm not
positive. If anyone can help me with this one I'd appreciate it.

Michael Gensel,
Livonia Tool & Laser
936 Anderson Road
Litchfield, MI 49252
ISO 9001:2000 Registered
Email: michaelg@...
Website: www.livoniatool.com
Phone: 888-875-0833
Fax: 517-542-2427






---------------------------------
Check out the hottest 2008 models today at Yahoo! Autos.

[Non-text portions of this message have been removed]
7
I am looking for some insight into ODBC connection configurations.
Anyone know what the following Advanced Connection parameters mean?



READ COMMITTED, READ UNCOMMITTED, REAPEATABLE READ, and SERIALIZABLE





Thanks in advanced.



Keith





---------------------------------
This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.

[Non-text portions of this message have been removed]
8
They're isolation levels.

Perhaps this'll help:

http://support.microsoft.com/kb/95022




-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Keith Mailloux
Sent: Wednesday, January 06, 2010 4:29 PM
To: vantage@yahoogroups.com
Subject: [Vantage] ODBC question

I am looking for some insight into ODBC connection configurations.
Anyone know what the following Advanced Connection parameters mean?



READ COMMITTED, READ UNCOMMITTED, REAPEATABLE READ, and SERIALIZABLE





Thanks in advanced.



Keith





---------------------------------
This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.

[Non-text portions of this message have been removed]



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
9
READ UNCOMMITTED is read only. The other three allow you to write back to the database, but I don't know what the differences are. You can find descriptions of them on the Internet if you can make sense of them. Only use READ UNCOMMITTED on a live multiuser Progress database or else you will lock users out of tables and records, not to mention that fact that writing to your Progress through ODBC has to potential of corrupting your entire database.




________________________________
From: Keith Mailloux <keith.mailloux@...>
To: vantage@yahoogroups.com
Sent: Wed, January 6, 2010 4:28:44 PM
Subject: [Vantage] ODBC question

Â
I am looking for some insight into ODBC connection configurations.
Anyone know what the following Advanced Connection parameters mean?

READ COMMITTED, READ UNCOMMITTED, REAPEATABLE READ, and SERIALIZABLE

Thanks in advanced.

Keith

------------ --------- --------- ---
This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.

[Non-text portions of this message have been removed]







[Non-text portions of this message have been removed]