ODBC / problem connecting certain tables

Greg,

Thanks! The Pass-Through worked. If I create the Pass-Through and rename it to PUB_ORDERDTL it looks like my Access programs will work without modification.

Oddly, I'm even able to connect to the Customer table via a Pass-Through which I thought would be impossible because Access wouldn't be able to handle the number of indexes.

Our plant manager is extremely computer literate and writes his own queries in Excel. I'll probably still need to keep working on the ODBC connection so that he can do his thing but Greg's advice will allow me to push forward in using Access to create EDI files to push into Service Connect. Thanks again Greg.

Incidentally, I have the 2 WordAround2 reg entries but they didn't fix the problem in my case.

I have installed a Progress hotfix but need to wait for a server reboot to see if that helps.

John Wapner
Bracalente Mfg.





--- In vantage@yahoogroups.com, Greg Renfro <greg.renfro@...> wrote:
>
> One correction, I meant to say title bar when referring to the path and password saving, not address bar. Sorry for any confusion.
>
> Greg Renfro
> IT Manager
> Apex Engineering International, LLC.
> 316-262-1494 x139
> ________________________________
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Greg Renfro
> Sent: Thursday, April 16, 2009 2:39 PM
> To: 'vantage@yahoogroups.com'
> Subject: RE: [Vantage] Re: ODBC / problem connecting certain tables
>
>
>
>
>
> I was referring to the passthrough query in Access. Create a new query in Access. Do not add any tables and choose Close, then right click in the window where your tables would normally be. Next choose SQL Specific from the pull down and choose Pass-Through. Then you would plug in the SQL code to execute against the table in question. Also you then can right click the address bar and set the ODBC path and password and save it in your query.
>
> Here is some example code:
>
> Select JobHead.ReqDueDate, JobHead.DueDate, JobHead.Company, JobHead.JobNum, JobHead.PartNum, JobHead.PartDescription, JobHead.JobClosed, JobHead.JobReleased, JobComplete from PUB.JobHead
>
> This will pull the listed fields from the Job Header table.
>
> Greg Renfro
> IT Manager
> Apex Engineering International, LLC.
> 316-262-1494 x139
> ________________________________
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of wapnerj
> Sent: Thursday, April 16, 2009 2:18 PM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: ODBC / problem connecting certain tables
>
> Hi Greg,
>
> I neglected to mention that we're running on Progress. In Vantage 6.1 there was something that I presume was similar - a server-based query that returned all the records from the table. You connected to that "view" rather than the actual table via ODBC. However, tech support said that's not available in OpenEdge.
>
> Is the above what you meant by a SQL view?
>
> I gather that the overall concensus of people is not to use SQL with Vantage, but does SQL (instead of Progress) resolve these ODBC connection issues?
>
> John Wapner
> Bracalente Mfg.
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>, Greg Renfro <greg.renfro@> wrote:
> >
> > Try using a SQL passthrough query. This has worked for me in most situations.
> >
> >
> > Greg Renfro
> > IT Manager
> > Apex Engineering International, LLC.
> > 316-262-1494 x139
> > ________________________________
> > From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>] On Behalf Of wapnerj
> > Sent: Thursday, April 16, 2009 1:33 PM
> > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] ODBC / problem connecting certain tables
> >
> >
> >
> >
> >
> > I'm working on setting up the ODBC connection on a test 8.03 server. I've gotten to the point that I can open some tables such as ORDERREL in Access 2007 but ORDERDTL causes Access to lockup and restart.
> >
> > Using the Data Dictionary utility I've set the width of comment fields from 2000 characters to 254 but still can't open the table. It does not seem to have an excessive number of indexes.
> >
> > The PARTBIN table returns a grid with #DELETED in every cell in Access.
> >
> > Other tables open correctly in Access.
> >
> > It sounds like other people have gotten ODBC working with 8.03 - any help would be appreciated.
> >
> > John Wapner
> > Bracalente Mfg.
> >
> >
> >
> > [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]
>
I'm working on setting up the ODBC connection on a test 8.03 server. I've gotten to the point that I can open some tables such as ORDERREL in Access 2007 but ORDERDTL causes Access to lockup and restart.

Using the Data Dictionary utility I've set the width of comment fields from 2000 characters to 254 but still can't open the table. It does not seem to have an excessive number of indexes.

The PARTBIN table returns a grid with #DELETED in every cell in Access.

Other tables open correctly in Access.

It sounds like other people have gotten ODBC working with 8.03 - any help would be appreciated.

John Wapner
Bracalente Mfg.
I worked on a project similar and some tables either due to being rather
large or some other reasons I don't understand won't play well with
access. My solution (good, bad, or otherwise), was to use Excel to
establish an ODBC connection to those naughty tables and then linked
access to that. Seemed to work in my situation anyhow...



Rob Bucek

Manufacturing Engineer

PH: 715-284-5376 ext 311

FAX: 715-284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site)



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of wapnerj
Sent: Thursday, April 16, 2009 1:33 PM
To: vantage@yahoogroups.com
Subject: [Vantage] ODBC / problem connecting certain tables





I'm working on setting up the ODBC connection on a test 8.03 server.
I've gotten to the point that I can open some tables such as ORDERREL in
Access 2007 but ORDERDTL causes Access to lockup and restart.

Using the Data Dictionary utility I've set the width of comment fields
from 2000 characters to 254 but still can't open the table. It does not
seem to have an excessive number of indexes.

The PARTBIN table returns a grid with #DELETED in every cell in Access.

Other tables open correctly in Access.

It sounds like other people have gotten ODBC working with 8.03 - any
help would be appreciated.

John Wapner
Bracalente Mfg.





[Non-text portions of this message have been removed]
Try using a SQL passthrough query. This has worked for me in most situations.


Greg Renfro
IT Manager
Apex Engineering International, LLC.
316-262-1494 x139
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of wapnerj
Sent: Thursday, April 16, 2009 1:33 PM
To: vantage@yahoogroups.com
Subject: [Vantage] ODBC / problem connecting certain tables





I'm working on setting up the ODBC connection on a test 8.03 server. I've gotten to the point that I can open some tables such as ORDERREL in Access 2007 but ORDERDTL causes Access to lockup and restart.

Using the Data Dictionary utility I've set the width of comment fields from 2000 characters to 254 but still can't open the table. It does not seem to have an excessive number of indexes.

The PARTBIN table returns a grid with #DELETED in every cell in Access.

Other tables open correctly in Access.

It sounds like other people have gotten ODBC working with 8.03 - any help would be appreciated.

John Wapner
Bracalente Mfg.



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

I neglected to mention that we're running on Progress. In Vantage 6.1 there was something that I presume was similar - a server-based query that returned all the records from the table. You connected to that "view" rather than the actual table via ODBC. However, tech support said that's not available in OpenEdge.

Is the above what you meant by a SQL view?

I gather that the overall concensus of people is not to use SQL with Vantage, but does SQL (instead of Progress) resolve these ODBC connection issues?

John Wapner
Bracalente Mfg.



--- In vantage@yahoogroups.com, Greg Renfro <greg.renfro@...> wrote:
>
> Try using a SQL passthrough query. This has worked for me in most situations.
>
>
> Greg Renfro
> IT Manager
> Apex Engineering International, LLC.
> 316-262-1494 x139
> ________________________________
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of wapnerj
> Sent: Thursday, April 16, 2009 1:33 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] ODBC / problem connecting certain tables
>
>
>
>
>
> I'm working on setting up the ODBC connection on a test 8.03 server. I've gotten to the point that I can open some tables such as ORDERREL in Access 2007 but ORDERDTL causes Access to lockup and restart.
>
> Using the Data Dictionary utility I've set the width of comment fields from 2000 characters to 254 but still can't open the table. It does not seem to have an excessive number of indexes.
>
> The PARTBIN table returns a grid with #DELETED in every cell in Access.
>
> Other tables open correctly in Access.
>
> It sounds like other people have gotten ODBC working with 8.03 - any help would be appreciated.
>
> John Wapner
> Bracalente Mfg.
>
>
>
> [Non-text portions of this message have been removed]
>
The advantages of SQL far outweigh any disadvantages in my opinion, is
that really the consensus out there?



Rob Bucek

Manufacturing Engineer

PH: 715-284-5376 ext 311

FAX: 715-284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site)



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of wapnerj
Sent: Thursday, April 16, 2009 2:18 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: ODBC / problem connecting certain tables





Hi Greg,

I neglected to mention that we're running on Progress. In Vantage 6.1
there was something that I presume was similar - a server-based query
that returned all the records from the table. You connected to that
"view" rather than the actual table via ODBC. However, tech support said
that's not available in OpenEdge.

Is the above what you meant by a SQL view?

I gather that the overall concensus of people is not to use SQL with
Vantage, but does SQL (instead of Progress) resolve these ODBC
connection issues?

John Wapner
Bracalente Mfg.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , Greg
Renfro <greg.renfro@...> wrote:
>
> Try using a SQL passthrough query. This has worked for me in most
situations.
>
>
> Greg Renfro
> IT Manager
> Apex Engineering International, LLC.
> 316-262-1494 x139
> ________________________________
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of wapnerj
> Sent: Thursday, April 16, 2009 1:33 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] ODBC / problem connecting certain tables
>
>
>
>
>
> I'm working on setting up the ODBC connection on a test 8.03 server.
I've gotten to the point that I can open some tables such as ORDERREL in
Access 2007 but ORDERDTL causes Access to lockup and restart.
>
> Using the Data Dictionary utility I've set the width of comment fields
from 2000 characters to 254 but still can't open the table. It does not
seem to have an excessive number of indexes.
>
> The PARTBIN table returns a grid with #DELETED in every cell in
Access.
>
> Other tables open correctly in Access.
>
> It sounds like other people have gotten ODBC working with 8.03 - any
help would be appreciated.
>
> John Wapner
> Bracalente Mfg.
>
>
>
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]
I was referring to the passthrough query in Access. Create a new query in Access. Do not add any tables and choose Close, then right click in the window where your tables would normally be. Next choose SQL Specific from the pull down and choose Pass-Through. Then you would plug in the SQL code to execute against the table in question. Also you then can right click the address bar and set the ODBC path and password and save it in your query.

Here is some example code:

Select JobHead.ReqDueDate, JobHead.DueDate, JobHead.Company, JobHead.JobNum, JobHead.PartNum, JobHead.PartDescription, JobHead.JobClosed, JobHead.JobReleased, JobComplete from PUB.JobHead

This will pull the listed fields from the Job Header table.

Greg Renfro
IT Manager
Apex Engineering International, LLC.
316-262-1494 x139
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of wapnerj
Sent: Thursday, April 16, 2009 2:18 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: ODBC / problem connecting certain tables





Hi Greg,

I neglected to mention that we're running on Progress. In Vantage 6.1 there was something that I presume was similar - a server-based query that returned all the records from the table. You connected to that "view" rather than the actual table via ODBC. However, tech support said that's not available in OpenEdge.

Is the above what you meant by a SQL view?

I gather that the overall concensus of people is not to use SQL with Vantage, but does SQL (instead of Progress) resolve these ODBC connection issues?

John Wapner
Bracalente Mfg.

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Greg Renfro <greg.renfro@...> wrote:
>
> Try using a SQL passthrough query. This has worked for me in most situations.
>
>
> Greg Renfro
> IT Manager
> Apex Engineering International, LLC.
> 316-262-1494 x139
> ________________________________
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of wapnerj
> Sent: Thursday, April 16, 2009 1:33 PM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] ODBC / problem connecting certain tables
>
>
>
>
>
> I'm working on setting up the ODBC connection on a test 8.03 server. I've gotten to the point that I can open some tables such as ORDERREL in Access 2007 but ORDERDTL causes Access to lockup and restart.
>
> Using the Data Dictionary utility I've set the width of comment fields from 2000 characters to 254 but still can't open the table. It does not seem to have an excessive number of indexes.
>
> The PARTBIN table returns a grid with #DELETED in every cell in Access.
>
> Other tables open correctly in Access.
>
> It sounds like other people have gotten ODBC working with 8.03 - any help would be appreciated.
>
> John Wapner
> Bracalente Mfg.
>
>
>
> [Non-text portions of this message have been removed]
>



[Non-text portions of this message have been removed]
One correction, I meant to say title bar when referring to the path and password saving, not address bar. Sorry for any confusion.

Greg Renfro
IT Manager
Apex Engineering International, LLC.
316-262-1494 x139
________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Greg Renfro
Sent: Thursday, April 16, 2009 2:39 PM
To: 'vantage@yahoogroups.com'
Subject: RE: [Vantage] Re: ODBC / problem connecting certain tables





I was referring to the passthrough query in Access. Create a new query in Access. Do not add any tables and choose Close, then right click in the window where your tables would normally be. Next choose SQL Specific from the pull down and choose Pass-Through. Then you would plug in the SQL code to execute against the table in question. Also you then can right click the address bar and set the ODBC path and password and save it in your query.

Here is some example code:

Select JobHead.ReqDueDate, JobHead.DueDate, JobHead.Company, JobHead.JobNum, JobHead.PartNum, JobHead.PartDescription, JobHead.JobClosed, JobHead.JobReleased, JobComplete from PUB.JobHead

This will pull the listed fields from the Job Header table.

Greg Renfro
IT Manager
Apex Engineering International, LLC.
316-262-1494 x139
________________________________
From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of wapnerj
Sent: Thursday, April 16, 2009 2:18 PM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: ODBC / problem connecting certain tables

Hi Greg,

I neglected to mention that we're running on Progress. In Vantage 6.1 there was something that I presume was similar - a server-based query that returned all the records from the table. You connected to that "view" rather than the actual table via ODBC. However, tech support said that's not available in OpenEdge.

Is the above what you meant by a SQL view?

I gather that the overall concensus of people is not to use SQL with Vantage, but does SQL (instead of Progress) resolve these ODBC connection issues?

John Wapner
Bracalente Mfg.

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>, Greg Renfro <greg.renfro@...> wrote:
>
> Try using a SQL passthrough query. This has worked for me in most situations.
>
>
> Greg Renfro
> IT Manager
> Apex Engineering International, LLC.
> 316-262-1494 x139
> ________________________________
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>] On Behalf Of wapnerj
> Sent: Thursday, April 16, 2009 1:33 PM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] ODBC / problem connecting certain tables
>
>
>
>
>
> I'm working on setting up the ODBC connection on a test 8.03 server. I've gotten to the point that I can open some tables such as ORDERREL in Access 2007 but ORDERDTL causes Access to lockup and restart.
>
> Using the Data Dictionary utility I've set the width of comment fields from 2000 characters to 254 but still can't open the table. It does not seem to have an excessive number of indexes.
>
> The PARTBIN table returns a grid with #DELETED in every cell in Access.
>
> Other tables open correctly in Access.
>
> It sounds like other people have gotten ODBC working with 8.03 - any help would be appreciated.
>
> John Wapner
> Bracalente Mfg.
>
>
>
> [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]
I think it is more about what you know, what you feel comfortable with, and what resources you have at your disposal. When 8.0 first came out, I had many discussions with folks from Epicor that said it did not matter what DB you used. I personally prefer SQL and have been able to do so much more with reporting, integration, and overall accessibility because I am more comfortable with SQL.

Joe Luster
Network Administrator
Cold Jet, LLC
455 Wards Corner Road
Loveland, Ohio 45140
USA
+1 513-831-3211 x308 (office)
+1 513-831-1209 (fax)
www.coldjet.com<http://www.coldjet.com>
[cid:image001.jpg@01C9BEAB.8CC2EE00]
Setting industry standards in dry ice technology and solutions for over 20 years.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Rob Bucek
Sent: Thursday, April 16, 2009 3:31 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: ODBC / problem connecting certain tables





The advantages of SQL far outweigh any disadvantages in my opinion, is
that really the consensus out there?

Rob Bucek

Manufacturing Engineer

PH: 715-284-5376 ext 311

FAX: 715-284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site)

________________________________

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
Of wapnerj
Sent: Thursday, April 16, 2009 2:18 PM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: ODBC / problem connecting certain tables

Hi Greg,

I neglected to mention that we're running on Progress. In Vantage 6.1
there was something that I presume was similar - a server-based query
that returned all the records from the table. You connected to that
"view" rather than the actual table via ODBC. However, tech support said
that's not available in OpenEdge.

Is the above what you meant by a SQL view?

I gather that the overall concensus of people is not to use SQL with
Vantage, but does SQL (instead of Progress) resolve these ODBC
connection issues?

John Wapner
Bracalente Mfg.

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> , Greg
Renfro <greg.renfro@...> wrote:
>
> Try using a SQL passthrough query. This has worked for me in most
situations.
>
>
> Greg Renfro
> IT Manager
> Apex Engineering International, LLC.
> 316-262-1494 x139
> ________________________________
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ] On
Behalf Of wapnerj
> Sent: Thursday, April 16, 2009 1:33 PM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] ODBC / problem connecting certain tables
>
>
>
>
>
> I'm working on setting up the ODBC connection on a test 8.03 server.
I've gotten to the point that I can open some tables such as ORDERREL in
Access 2007 but ORDERDTL causes Access to lockup and restart.
>
> Using the Data Dictionary utility I've set the width of comment fields
from 2000 characters to 254 but still can't open the table. It does not
seem to have an excessive number of indexes.
>
> The PARTBIN table returns a grid with #DELETED in every cell in
Access.
>
> Other tables open correctly in Access.
>
> It sounds like other people have gotten ODBC working with 8.03 - any
help would be appreciated.
>
> John Wapner
> Bracalente Mfg.
>
>
>
> [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]
That's a big part of it..the resource pool (human capital) that is
available to support that platform.



Rob Bucek

Manufacturing Engineer

PH: 715-284-5376 ext 311

FAX: 715-284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site)



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Joe Luster
Sent: Thursday, April 16, 2009 3:05 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: ODBC / problem connecting certain tables





I think it is more about what you know, what you feel comfortable with,
and what resources you have at your disposal. When 8.0 first came out, I
had many discussions with folks from Epicor that said it did not matter
what DB you used. I personally prefer SQL and have been able to do so
much more with reporting, integration, and overall accessibility because
I am more comfortable with SQL.

Joe Luster
Network Administrator
Cold Jet, LLC
455 Wards Corner Road
Loveland, Ohio 45140
USA
+1 513-831-3211 x308 (office)
+1 513-831-1209 (fax)
www.coldjet.com<http://www.coldjet.com <http://www.coldjet.com> >
[cid:image001.jpg@01C9BEAB.8CC2EE00
<mailto:image001.jpg%4001C9BEAB.8CC2EE00> ]
Setting industry standards in dry ice technology and solutions for over
20 years.

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of Rob Bucek
Sent: Thursday, April 16, 2009 3:31 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] Re: ODBC / problem connecting certain tables

The advantages of SQL far outweigh any disadvantages in my opinion, is
that really the consensus out there?

Rob Bucek

Manufacturing Engineer

PH: 715-284-5376 ext 311

FAX: 715-284-4084

<http://www.dsmfg.com/ <http://www.dsmfg.com/> >

(Click the logo to view our site)

________________________________

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>]
On Behalf
Of wapnerj
Sent: Thursday, April 16, 2009 2:18 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: ODBC / problem connecting certain tables

Hi Greg,

I neglected to mention that we're running on Progress. In Vantage 6.1
there was something that I presume was similar - a server-based query
that returned all the records from the table. You connected to that
"view" rather than the actual table via ODBC. However, tech support said
that's not available in OpenEdge.

Is the above what you meant by a SQL view?

I gather that the overall concensus of people is not to use SQL with
Vantage, but does SQL (instead of Progress) resolve these ODBC
connection issues?

John Wapner
Bracalente Mfg.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ,
Greg
Renfro <greg.renfro@...> wrote:
>
> Try using a SQL passthrough query. This has worked for me in most
situations.
>
>
> Greg Renfro
> IT Manager
> Apex Engineering International, LLC.
> 316-262-1494 x139
> ________________________________
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com> ]
On
Behalf Of wapnerj
> Sent: Thursday, April 16, 2009 1:33 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] ODBC / problem connecting certain tables
>
>
>
>
>
> I'm working on setting up the ODBC connection on a test 8.03 server.
I've gotten to the point that I can open some tables such as ORDERREL in
Access 2007 but ORDERDTL causes Access to lockup and restart.
>
> Using the Data Dictionary utility I've set the width of comment fields
from 2000 characters to 254 but still can't open the table. It does not
seem to have an excessive number of indexes.
>
> The PARTBIN table returns a grid with #DELETED in every cell in
Access.
>
> Other tables open correctly in Access.
>
> It sounds like other people have gotten ODBC working with 8.03 - any
help would be appreciated.
>
> John Wapner
> Bracalente Mfg.
>
>
>
> [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]





[Non-text portions of this message have been removed]
There are some registry patches to make that will allow Access to work.
You have to tell Access to use 8K instead of the default
Â
The name of the key to add is Workarrounds2
Â
edit the registry and add a new string value to your ODBC.INI
 Â
WorkArounds2 = 8192 in \Software\ODBC\ODBC.INI\Your_DSN using regedit.exe
Â
Let me know if you need help and I will try to find the instructions.

--- On Thu, 4/16/09, wapnerj <jwapner@...> wrote:

From: wapnerj <jwapner@...>
Subject: [Vantage] ODBC / problem connecting certain tables
To: vantage@yahoogroups.com
Date: Thursday, April 16, 2009, 1:32 PM








I'm working on setting up the ODBC connection on a test 8.03 server. I've gotten to the point that I can open some tables such as ORDERREL in Access 2007 but ORDERDTL causes Access to lockup and restart.

Using the Data Dictionary utility I've set the width of comment fields from 2000 characters to 254 but still can't open the table. It does not seem to have an excessive number of indexes.

The PARTBIN table returns a grid with #DELETED in every cell in Access.

Other tables open correctly in Access.

It sounds like other people have gotten ODBC working with 8.03 - any help would be appreciated.

John Wapner
Bracalente Mfg.



















[Non-text portions of this message have been removed]
I tried this for a Crystal issue and it didn't really seem to help my
problem. I had a massive query that was being sent across and it would
throw a fit cuz it was too long. I didn't have much luck with this fix for
that problem but maybe it will be better for you.



I'm sure the progress / ODBC version you are using will also make a
difference.



~Charlie

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
DD
Sent: Thursday, April 16, 2009 5:04 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] ODBC / problem connecting certain tables








There are some registry patches to make that will allow Access to work.
You have to tell Access to use 8K instead of the default

The name of the key to add is Workarrounds2

edit the registry and add a new string value to your ODBC.INI

WorkArounds2 = 8192 in \Software\ODBC\ODBC.INI\Your_DSN using regedit.exe

Let me know if you need help and I will try to find the instructions.

--- On Thu, 4/16/09, wapnerj <jwapner@bracalente.
<mailto:jwapner%40bracalente.com> com> wrote:

From: wapnerj <jwapner@bracalente. <mailto:jwapner%40bracalente.com> com>
Subject: [Vantage] ODBC / problem connecting certain tables
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Date: Thursday, April 16, 2009, 1:32 PM

I'm working on setting up the ODBC connection on a test 8.03 server. I've
gotten to the point that I can open some tables such as ORDERREL in Access
2007 but ORDERDTL causes Access to lockup and restart.

Using the Data Dictionary utility I've set the width of comment fields from
2000 characters to 254 but still can't open the table. It does not seem to
have an excessive number of indexes.

The PARTBIN table returns a grid with #DELETED in every cell in Access.

Other tables open correctly in Access.

It sounds like other people have gotten ODBC working with 8.03 - any help
would be appreciated.

John Wapner
Bracalente Mfg.

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





[Non-text portions of this message have been removed]
It will fix many of his problems. It is an Access problem so should not change Crystal.Â
It will fix the #Deleted problems but not the too many indexes on the customer table.
Â
Here is the old writeup on Microsoft. I know it is a problem with Access 2003 also. I do not know about later versions.
Â
WorkArounds2=8192. Workaround for Microsoft Access 2000 when it calls
SQLStatisticsW and SQLGetData for column number 10. Microsoft Access
only asks for the data as a two-byte SQL_C_WCHAR, which is insufficient
buffer to store the UCS2 character and the null terminator.


--- On Thu, 4/16/09, Charlie Wilson <foamdesigncsw@...> wrote:

From: Charlie Wilson <foamdesigncsw@...>
Subject: RE: [Vantage] ODBC / problem connecting certain tables
To: vantage@yahoogroups.com
Date: Thursday, April 16, 2009, 4:15 PM








I tried this for a Crystal issue and it didn't really seem to help my
problem. I had a massive query that was being sent across and it would
throw a fit cuz it was too long. I didn't have much luck with this fix for
that problem but maybe it will be better for you.

I'm sure the progress / ODBC version you are using will also make a
difference.

~Charlie

_____

From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf Of
DD
Sent: Thursday, April 16, 2009 5:04 PM
To: vantage@yahoogroups .com
Subject: Re: [Vantage] ODBC / problem connecting certain tables

There are some registry patches to make that will allow Access to work.
You have to tell Access to use 8K instead of the default

The name of the key to add is Workarrounds2

edit the registry and add a new string value to your ODBC.INI

WorkArounds2 = 8192 in \Software\ODBC\ ODBC.INI\ Your_DSN using regedit.exe

Let me know if you need help and I will try to find the instructions.

--- On Thu, 4/16/09, wapnerj <jwapner@bracalente .
<mailto:jwapner% 40bracalente. com> com> wrote:

From: wapnerj <jwapner@bracalente . <mailto:jwapner% 40bracalente. com> com>
Subject: [Vantage] ODBC / problem connecting certain tables
To: vantage@yahoogroups <mailto:vantage% 40yahoogroups. com> .com
Date: Thursday, April 16, 2009, 1:32 PM

I'm working on setting up the ODBC connection on a test 8.03 server. I've
gotten to the point that I can open some tables such as ORDERREL in Access
2007 but ORDERDTL causes Access to lockup and restart.

Using the Data Dictionary utility I've set the width of comment fields from
2000 characters to 254 but still can't open the table. It does not seem to
have an excessive number of indexes.

The PARTBIN table returns a grid with #DELETED in every cell in Access.

Other tables open correctly in Access.

It sounds like other people have gotten ODBC working with 8.03 - any help
would be appreciated.

John Wapner
Bracalente Mfg.

[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]
Â
Here are the Instructions from the Progress knowledge base:
It said that Access 2007 also needed the patch.

To resolve this error, set WorkArounds2=8192 for the affected data source. This can be done by using the Registry Editor (RegEdit).

1. Run RegEdit

2. Locate the ODBC DSN in the Registry:

For a USER Data Source, go to HKEY_CURRENT_USER -> Software -> ODBC -> ODBC.INI -> YourDataSourceName
For a SYSTEM Data Source, go to HKEY_LOCAL_MACHINE -> Software -> ODBC -> ODBC.INI -> YourDataSourceName

3. Click on the folder for your data source; from the menu choose:
Edit -> New -> String Value

4. Set the name of the new string value to be WorkArounds2

5. Double click on WorkArounds2 in the right hand panel; this will bring up a dialog box with a data value field

6. Change the data value to 8192

7. Click OK

8. Close RegEdit

--- On Thu, 4/16/09, DD <ddavis4569@...> wrote:

From: DD <ddavis4569@...>
Subject: RE: [Vantage] ODBC / problem connecting certain tables
To: vantage@yahoogroups.com
Date: Thursday, April 16, 2009, 4:31 PM








It will fix many of his problems. It is an Access problem so should not change Crystal.Â
It will fix the #Deleted problems but not the too many indexes on the customer table.
Â
Here is the old writeup on Microsoft. I know it is a problem with Access 2003 also. I do not know about later versions.
Â
WorkArounds2= 8192. Workaround for Microsoft Access 2000 when it calls
SQLStatisticsW and SQLGetData for column number 10. Microsoft Access
only asks for the data as a two-byte SQL_C_WCHAR, which is insufficient
buffer to store the UCS2 character and the null terminator.

--- On Thu, 4/16/09, Charlie Wilson <foamdesigncsw@ yahoo.com> wrote:

From: Charlie Wilson <foamdesigncsw@ yahoo.com>
Subject: RE: [Vantage] ODBC / problem connecting certain tables
To: vantage@yahoogroups .com
Date: Thursday, April 16, 2009, 4:15 PM

I tried this for a Crystal issue and it didn't really seem to help my
problem. I had a massive query that was being sent across and it would
throw a fit cuz it was too long. I didn't have much luck with this fix for
that problem but maybe it will be better for you.

I'm sure the progress / ODBC version you are using will also make a
difference.

~Charlie

_____

From: vantage@yahoogroups .com [mailto:vantage@ yahoogroups .com] On Behalf Of
DD
Sent: Thursday, April 16, 2009 5:04 PM
To: vantage@yahoogroups .com
Subject: Re: [Vantage] ODBC / problem connecting certain tables

There are some registry patches to make that will allow Access to work.
You have to tell Access to use 8K instead of the default

The name of the key to add is Workarrounds2

edit the registry and add a new string value to your ODBC.INI

WorkArounds2 = 8192 in \Software\ODBC\ ODBC.INI\ Your_DSN using regedit.exe

Let me know if you need help and I will try to find the instructions.

--- On Thu, 4/16/09, wapnerj <jwapner@bracalente .
<mailto:jwapner% 40bracalente. com> com> wrote:

From: wapnerj <jwapner@bracalente . <mailto:jwapner% 40bracalente. com> com>
Subject: [Vantage] ODBC / problem connecting certain tables
To: vantage@yahoogroups <mailto:vantage% 40yahoogroups. com> .com
Date: Thursday, April 16, 2009, 1:32 PM

I'm working on setting up the ODBC connection on a test 8.03 server. I've
gotten to the point that I can open some tables such as ORDERREL in Access
2007 but ORDERDTL causes Access to lockup and restart.

Using the Data Dictionary utility I've set the width of comment fields from
2000 characters to 254 but still can't open the table. It does not seem to
have an excessive number of indexes.

The PARTBIN table returns a grid with #DELETED in every cell in Access.

Other tables open correctly in Access.

It sounds like other people have gotten ODBC working with 8.03 - any help
would be appreciated.

John Wapner
Bracalente Mfg.

[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]



















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