Getting ODBC to work

>> Is the return of the ### on scrolling not just because more fields have
been
returned than access can handle, I presume you query limits the result some
way?



Yes, I agree. I filter for what I want with the query.



Ross



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Tim Stevenson
Sent: Sunday, June 29, 2008 7:35 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Getting ODBC to work



Ross,

Is the return of the ### on scrolling not just because more fields have been
returned than access can handle, I presume you query limits the result some
way? I was having the same issue when I tried cccess and msquery on the
change log and the only way to get a result was to limit the number of
records returned by the query, my end solution was just to use a query from
VB as this does not have the same restrictions.

Tim Stevenson

_____

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of
Ross Hughes
Sent: Sunday, 29 June 2008 12:15 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: Getting ODBC to work

Views are SQL views that are basically queries that wrap over the table.
These are required to read some tables because they have multiple indexes in
Progress and Access wants them to have one.

Customer table needs a view. It seems like there is one with Jobs, I can't
remember which one right now.maybe JobOper. You will get the error about
'too many indexes' and have to create a view.

Most of the tables you can access directly.some just need adjustment.

The special considerations are me saying this is kind of clunky and yet
works. You will get field length errors on some tables. If that happens
you need to go to the Progress db administration tool and change the lengths
of the fields. There are instructions for this when you run across this.

I also run in to the data in a table only presenting itself until you start
to scroll through the table.then it all turns to # signs. The only way I
can consistently return the data in these situations is with a Access query
wrapped around it..especially when I am filtering something off.

All and all, I am a big fan of using Access as an all-purpose tool. It is
so flexible and easy to access things once you get it connected.

Ross

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
Behalf Of
Thomas Rose
Sent: Friday, June 27, 2008 5:16 PM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Subject: RE: {Disarmed} [Vantage] Re: Getting ODBC to work

I feel like I am working on a jigsaw puzzle. I have all the pieces turned
picture side up and now I just have to put it all together.

Your last paragraph is something I'm trying to take in, and seems to raise
more questions:

- Where are the views?

- Which tables have views?

- Are there any tables I can access directly?

- What are the "special considerations" needed for the other tables?

I apologize for sounding completely dense about this subject. I am used to
linking SQL Server tables using ODBC into Access databases and, so far, that
is a lot easier. Of course, if I think about it long enough, I will probably
realize it took me just as long to get up to speed on that use of ODBC.

In any case, I do appreciate everyone's help so far!

Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electric <http://www.electricmirror.com/>
mirror.com/>

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com> ] On
Behalf Of Ross Hughes
Sent: Thursday, June 26, 2008 2:18 PM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
Subject: {Disarmed} [Vantage] Re: Getting ODBC to work

The registry modification will work for all Access versions that I
have tried - 00,03,07. I am currently using 07.

I only needed to modify the CURRENT_USER node of the registry tree
and used a value of 40960 for my Workaround2 string.

In Access you will only have a SAVE PASSWORD box in the linked fields
process. The rest it is managed at the ODBC level.

If are successful with the Test Connection process via ODBC then that
username/password issue should be taken care of.

Also, it depends on what tables you are talking about. For example,
the customer table needs a view and many of the other tables need
special considerations as well through Access.

Ross

--- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>, Thomas Rose <t.rose@...> wrote:
>
> Matt, Ross, and Vic,
>
> Thank you for your input. I am getting closer. Ross's advice
about the addition of WorkArounds2 to the registry, in particular,
seemed to get me closer. I tried with each of the values suggested.
I'm wondering, do those values apply to Access 2003 and Access 2000?
Is there another value that applies to Access 2007, the version I am
on?
>
> Vic, sorry about not supplying version number: 8.03.403D
>
> I have gotten far enough that I can see (in either Access or
Crystal) the tables in the database and the fields. I think your
answer primarily addresses those issues. I cannot see the data in
the tables, though. The one thing that your answer may be shedding
light on, though I am perhaps too dense to see, is a password issue.
If I use the user ID sysprogress, I do not have a valid password that
will even let me see the database. If I use the user ID and password
I use to log on normally, I can see the database, tables, and fields,
but not the data. Do I need to get the sysprogress password from my
administrator?
>
> Thank you for the help.
>
> Thom Rose
> Controller
> Electric Mirror, LLC
> T 425 776-4946 ext. 1024
> A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
> www.electricmirror.com<http://www.electric
<http://www.electricmirror.com/> mirror.com/>
>
> From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups
<mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>] On
Behalf Of Vic Drecchio
> Sent: Thursday, June 26, 2008 12:14 PM
> To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
> Cc: Thomas Rose
> Subject: {Disarmed} RE: [Vantage] Getting ODBC to work
>
>
> Tom, what version of Vantage? I'll assume 8.x.
>
> See if this helps you any: I also attached a more visual instruction
> sheet.
>
> Vic
>
> ++++++++++++++++++++++++++++++++++
> AnswerBook #: 7439MPS Product: Vantage
>
> Date Added: 10/30/2006 Version:
>
> Date Changed: 12/21/2006 Module: Installation
>
> Summary:
>
> 8.0 ODBC Setup - DataDirect 4.20 32-Bit Progress SQL92 v10.0B
>
> Details:
>
> PROBLEM DESCRIPTION: How to setup the ODBC Driver for MFGSYS version
> 8.0.
>
> PROBLEM RESOLUTION: Below are steps to setup the DataDirect 4.20 32-
Bit
> Progress SQL92
>
> v10.0B Driver for Mfgsys version 8.0.
>
> STEPS:
>
> 1) Using windows explorer, browse to your
server\epicor\oe100b\netsetup
> folder.
>
> 2) Double click on the SETUP.EXE in the netsetup folder which will
> install the "OpenEdge 10.B
>
> Shared Network Setup. For the working directory, you can point to
the
> shared folder on the
>
> server. (i.e. C:\epicor\mfgwrk80)
>
> 3) Create and open a new Text document at a workstation (i.e
ODBC.TXT).
>
> 4) Copy and paste all of the text below into that new (ODBC.TXT)
text
> doc.
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\DataDirect 4.20 32-
Bit
> Progress
>
> SQL92 v10.0B]
>
> "APILevel"="1"
>
> "ConnectFunctions"="YYN"
>
> "CPTimeout"="60"
>
> "Driver"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019.DLL<file://
/\\\servername\epicor\oe100b\bin\PGPRO1019.DLL>"
>
> "DriverODBCVer"="4.20"
>
> "FileUsage"="0"
>
> "Setup"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019S.DLL<file://
/\\\servername\epicor\oe100b\bin\PGPRO1019S.DLL>"
>
> "SQLLevel"="0"
>
> "UsageCount"="1"
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]
>
> "DataDirect 4.20 32-Bit Progress SQL92 v10.0B"="Installed"
>
> 5) Edit two lines of the text document to reflect your servers
name. The
> two lines are: "Driver ="
>
> and "Setup=". Change the \\Servername<file:/// <file:///\\> <file:///
<file:///\\> \\> <file:/// <file:///\\>
<file:/// <file:///\\> \\> \\> <file:/// <file:///\\> <file:///
<file:///\\> \\>
<file:/// <file:///\\> <file:/// <file:///\\> \\> \\> \\>\\Servername> to
your
servers actual name. Save
> the changes.
>
> 6) Rename the ODBC.TXT doc to ODBC.REG. This will change the
appearance
> of the file and
>
> allow it to be added to the registry.
>
> 7) Double click on the ODBC.REG file which will automatically
import the
> information into the
>
> workstations registry.
>
> Setup the ODBC DSN for the new DataDirect driver.
>
> ==========================================
>
> 8) Go to [Start] --> Settings --> Control Panel --> Administrative
Tools
> --> Data Sources
>
> (ODBC)
>
> 9) Click on the [System] tab, then the [ADD] button.
>
> 10) Scroll down and locate the "DataDirect 4.20 32-Bit Progress
SQL92
> v10.0B" driver, hightlight
>
> and click [FINISH].
>
> 11) Fill in the Properties window for the ODBC Progress OpenEdge
Driver
> Setup.
>
> - Data Source Name: OpenEdge10B (do not use spaces in the name)
>
> - Description: OpenEdge 10B
>
> - Host Name: <enter your servers name here>
>
> - Port Number: 8050 (for the Live database) 8060 (for the Training
> database), 8070 (for test)
>
> - Database Name: mfgsys
>
> - User ID: sysprogress (or the name you have chosen and setup in
your
> 6.x database.)
>
> - Click on the Advanced tab and set the Default Isolation Level to
Read
> Uncommited
>
> 12) Click on [Apply] and then press [Test Connect]
>
> 13) Fill in the password, click [OK]. You should get "Connection
> Established!". Click [OK]
>
> USER NAME and PASSWORD Setup:
>
> ================================
>
> NOTE If this is a new setup in that your database is either a new
> install or has never been setup
>
> to use ODBC, you will need to add an administrative user and
password to
> the database directly.
>
> Follow the remaining steps below to setup user: "sysprogress" and a
> password of your choice.
>
> 14) On the server or your Admin workstation if you have one setup,
make
> a copy of your
>
> "SchemaChange" icon.
>
> 15) Rename the copied icon to "ODBC Setup".
>
> 16) Right mouse click the ODBC Setup icon and select "Properties".
>
> 17) On the ShortCut tab, Target line, change the last parameter on
the
> line from: applydf.w to
>
> _admin.p Save the changes and double click.
>
> 18) In the Progress Database Administration utility, select ADMIN --
>
> SECURITY --> EDIT USER
>
> LIST.
>
> 19) Click on [ADD], and fill in the following fields
>
> - User ID: sysprogress
>
> - User name: sysprogress
>
> - Password: <this is your choice, do not forget what you entered>
>
> 20) Click [OK], and click [OK] again. Exit the Data Administration
> session.
>
> 21) You should now be able to go back and "Test Connect" your DSN
with
> the User ID and
>
> Password you just entered.
>
> Note: if any problems with the registry entries, make sure you
break it
> up into lines
>
> "key" = "Value"
>
> ________________________________
>
> From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>] On
Behalf
> Of Thomas Rose
> Sent: Thursday, June 26, 2008 3:03 PM
> To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Getting ODBC to work
>
> I thought I was having some success getting ODBC to work for me. I
am
> finally able to see the database tables (after many failures), but
I get
> error messages now when I try to get data from the tables:
> -When I try to link or import a table in Access I get the error
message
> "Reserved error (-7748); there is no message for this error."
> -When I try to get data in a Crystal report, I get the error message
> "Failed to retrieve data from the database. Details: HY000:
> [DataDirect][ODBC Progress OpenEdge Wire Protocol
> driver][OPENEDGE]Access denied (Authorization failed)(7512)[Database
> Vendor Code: -20228 ]".
>
> Any thoughts?
>
> Thom Rose
> Controller
> Electric Mirror, LLC
> T 425 776-4946 ext. 1024
> A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
> www.electricmirror.com<http://www.electric
<http://www.electricmirror.com/> mirror.com/
> <http://www.electric <http://www.electricmirror.com/> mirror.com/> >
>
> [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]

[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 thought I was having some success getting ODBC to work for me. I am finally able to see the database tables (after many failures), but I get error messages now when I try to get data from the tables:
-When I try to link or import a table in Access I get the error message "Reserved error (-7748); there is no message for this error."
-When I try to get data in a Crystal report, I get the error message "Failed to retrieve data from the database. Details: HY000: [DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Access denied (Authorization failed)(7512)[Database Vendor Code: -20228 ]".

Any thoughts?

Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com/>


[Non-text portions of this message have been removed]
Tom, what version of Vantage? I'll assume 8.x.

See if this helps you any: I also attached a more visual instruction
sheet.

Vic

++++++++++++++++++++++++++++++++++
AnswerBook #: 7439MPS Product: Vantage

Date Added: 10/30/2006 Version:

Date Changed: 12/21/2006 Module: Installation

Summary:

8.0 ODBC Setup - DataDirect 4.20 32-Bit Progress SQL92 v10.0B

Details:

PROBLEM DESCRIPTION: How to setup the ODBC Driver for MFGSYS version
8.0.

PROBLEM RESOLUTION: Below are steps to setup the DataDirect 4.20 32-Bit
Progress SQL92

v10.0B Driver for Mfgsys version 8.0.

STEPS:

1) Using windows explorer, browse to your server\epicor\oe100b\netsetup
folder.

2) Double click on the SETUP.EXE in the netsetup folder which will
install the "OpenEdge 10.B

Shared Network Setup. For the working directory, you can point to the
shared folder on the

server. (i.e. C:\epicor\mfgwrk80)

3) Create and open a new Text document at a workstation (i.e ODBC.TXT).

4) Copy and paste all of the text below into that new (ODBC.TXT) text
doc.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\DataDirect 4.20 32-Bit
Progress

SQL92 v10.0B]

"APILevel"="1"

"ConnectFunctions"="YYN"

"CPTimeout"="60"

"Driver"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019.DLL"

"DriverODBCVer"="4.20"

"FileUsage"="0"

"Setup"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019S.DLL"

"SQLLevel"="0"

"UsageCount"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]

"DataDirect 4.20 32-Bit Progress SQL92 v10.0B"="Installed"

5) Edit two lines of the text document to reflect your servers name. The
two lines are: "Driver ="

and "Setup=". Change the \\Servername to your servers actual name. Save
the changes.

6) Rename the ODBC.TXT doc to ODBC.REG. This will change the appearance
of the file and

allow it to be added to the registry.

7) Double click on the ODBC.REG file which will automatically import the
information into the

workstations registry.

Setup the ODBC DSN for the new DataDirect driver.

==========================================

8) Go to [Start] --> Settings --> Control Panel --> Administrative Tools
--> Data Sources

(ODBC)

9) Click on the [System] tab, then the [ADD] button.

10) Scroll down and locate the "DataDirect 4.20 32-Bit Progress SQL92
v10.0B" driver, hightlight

and click [FINISH].

11) Fill in the Properties window for the ODBC Progress OpenEdge Driver
Setup.

- Data Source Name: OpenEdge10B (do not use spaces in the name)

- Description: OpenEdge 10B

- Host Name: <enter your servers name here>

- Port Number: 8050 (for the Live database) 8060 (for the Training
database), 8070 (for test)

- Database Name: mfgsys

- User ID: sysprogress (or the name you have chosen and setup in your
6.x database.)

- Click on the Advanced tab and set the Default Isolation Level to Read
Uncommited

12) Click on [Apply] and then press [Test Connect]

13) Fill in the password, click [OK]. You should get "Connection
Established!". Click [OK]

USER NAME and PASSWORD Setup:

================================

NOTE If this is a new setup in that your database is either a new
install or has never been setup

to use ODBC, you will need to add an administrative user and password to
the database directly.

Follow the remaining steps below to setup user: "sysprogress" and a
password of your choice.

14) On the server or your Admin workstation if you have one setup, make
a copy of your

"SchemaChange" icon.

15) Rename the copied icon to "ODBC Setup".

16) Right mouse click the ODBC Setup icon and select "Properties".

17) On the ShortCut tab, Target line, change the last parameter on the
line from: applydf.w to

_admin.p Save the changes and double click.

18) In the Progress Database Administration utility, select ADMIN -->
SECURITY --> EDIT USER

LIST.

19) Click on [ADD], and fill in the following fields

- User ID: sysprogress

- User name: sysprogress

- Password: <this is your choice, do not forget what you entered>

20) Click [OK], and click [OK] again. Exit the Data Administration
session.

21) You should now be able to go back and "Test Connect" your DSN with
the User ID and

Password you just entered.

Note: if any problems with the registry entries, make sure you break it
up into lines

"key" = "Value"


________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Thomas Rose
Sent: Thursday, June 26, 2008 3:03 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Getting ODBC to work



I thought I was having some success getting ODBC to work for me. I am
finally able to see the database tables (after many failures), but I get
error messages now when I try to get data from the tables:
-When I try to link or import a table in Access I get the error message
"Reserved error (-7748); there is no message for this error."
-When I try to get data in a Crystal report, I get the error message
"Failed to retrieve data from the database. Details: HY000:
[DataDirect][ODBC Progress OpenEdge Wire Protocol
driver][OPENEDGE]Access denied (Authorization failed)(7512)[Database
Vendor Code: -20228 ]".

Any thoughts?

Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com/
<http://www.electricmirror.com/> >

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






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

There is an AB page for this. It needs a registry workaround.

It does work. I've used it successfully.

Here are the instructions:
------------------
Summary:

ODBC Reserved error (-7748); there is no message for this error, from
Access


Detail:


PROBLEM: User gets the following error while connecting from MS
Access 2000 or 2003 to the Vantage DB through an ODBC connection:

Titlebar shows: "Microsoft Office Access"
Message body shows: "Reserved error (-7748); there is no message for
this error."

XA800
XA803

RESOLUTION: This error is an MS Access error, not a OE 10.1B ODBC
error. A search for this errors shows several different versions of
MS Access that fails.

From MS Access Help:
Add a New String Value to the following Registry Keys
\\HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\(YOUR_DSN_NAME)
\\HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\(YOUR_DSN_NAME)

New String Name = WorkArounds2
Value = 40960
OR
Value = 8192

NOTE: Support recommends being familiar with editing the Registry
before implementing this solution.
-------------------

--- In vantage@yahoogroups.com, Thomas Rose <t.rose@...> wrote:
>
> I thought I was having some success getting ODBC to work for me. I
am finally able to see the database tables (after many failures), but
I get error messages now when I try to get data from the tables:
> -When I try to link or import a table in Access I get the error
message "Reserved error (-7748); there is no message for this error."
> -When I try to get data in a Crystal report, I get the error
message "Failed to retrieve data from the database. Details: HY000:
[DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]
Access denied (Authorization failed)(7512)[Database Vendor Code: -
20228 ]".
>
> Any thoughts?
>
> Thom Rose
> Controller
> Electric Mirror, LLC
> T 425 776-4946 ext. 1024
> A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
> www.electricmirror.com<http://www.electricmirror.com/>
>
>
> [Non-text portions of this message have been removed]
>
We run the network install from the c:\epicor\oe101b\netsetup directory.
Then we have a reg file that we run. That file contains:



Windows Registry Editor Version 5.00



[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\OpenEdge 10.1B driver]

"ConnectFunctions"="YYY"

"CPTimeout"="60"

"Driver"="\\\\vantage\\epicor\\oe101b\\bin\\pgoe1022.dll"

"DriverODBCVer"="5.1"

"FileUsage"="0"

"Setup"="\\\\vantage\\epicor\\oe101b\\bin\\pgoe1022.dll"

"SQLLevel"="1"

"UsageCount"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]

"OpenEdge 10.1B driver"="Installed"



Once we run that, we can connect up using ODBC....



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Thomas Rose
Sent: Thursday, June 26, 2008 2:03 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Getting ODBC to work



I thought I was having some success getting ODBC to work for me. I am
finally able to see the database tables (after many failures), but I get
error messages now when I try to get data from the tables:
-When I try to link or import a table in Access I get the error message
"Reserved error (-7748); there is no message for this error."
-When I try to get data in a Crystal report, I get the error message
"Failed to retrieve data from the database. Details: HY000:
[DataDirect][ODBC Progress OpenEdge Wire Protocol
driver][OPENEDGE]Access denied (Authorization failed)(7512)[Database
Vendor Code: -20228 ]".

Any thoughts?

Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com/>

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





[Non-text portions of this message have been removed]
Matt, Ross, and Vic,

Thank you for your input. I am getting closer. Ross's advice about the addition of WorkArounds2 to the registry, in particular, seemed to get me closer. I tried with each of the values suggested. I'm wondering, do those values apply to Access 2003 and Access 2000? Is there another value that applies to Access 2007, the version I am on?

Vic, sorry about not supplying version number: 8.03.403D

I have gotten far enough that I can see (in either Access or Crystal) the tables in the database and the fields. I think your answer primarily addresses those issues. I cannot see the data in the tables, though. The one thing that your answer may be shedding light on, though I am perhaps too dense to see, is a password issue. If I use the user ID sysprogress, I do not have a valid password that will even let me see the database. If I use the user ID and password I use to log on normally, I can see the database, tables, and fields, but not the data. Do I need to get the sysprogress password from my administrator?

Thank you for the help.

Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Vic Drecchio
Sent: Thursday, June 26, 2008 12:14 PM
To: vantage@yahoogroups.com
Cc: Thomas Rose
Subject: {Disarmed} RE: [Vantage] Getting ODBC to work


Tom, what version of Vantage? I'll assume 8.x.

See if this helps you any: I also attached a more visual instruction
sheet.

Vic

++++++++++++++++++++++++++++++++++
AnswerBook #: 7439MPS Product: Vantage

Date Added: 10/30/2006 Version:

Date Changed: 12/21/2006 Module: Installation

Summary:

8.0 ODBC Setup - DataDirect 4.20 32-Bit Progress SQL92 v10.0B

Details:

PROBLEM DESCRIPTION: How to setup the ODBC Driver for MFGSYS version
8.0.

PROBLEM RESOLUTION: Below are steps to setup the DataDirect 4.20 32-Bit
Progress SQL92

v10.0B Driver for Mfgsys version 8.0.

STEPS:

1) Using windows explorer, browse to your server\epicor\oe100b\netsetup
folder.

2) Double click on the SETUP.EXE in the netsetup folder which will
install the "OpenEdge 10.B

Shared Network Setup. For the working directory, you can point to the
shared folder on the

server. (i.e. C:\epicor\mfgwrk80)

3) Create and open a new Text document at a workstation (i.e ODBC.TXT).

4) Copy and paste all of the text below into that new (ODBC.TXT) text
doc.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\DataDirect 4.20 32-Bit
Progress

SQL92 v10.0B]

"APILevel"="1"

"ConnectFunctions"="YYN"

"CPTimeout"="60"

"Driver"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019.DLL<file:///\\\servername\epicor\oe100b\bin\PGPRO1019.DLL>"

"DriverODBCVer"="4.20"

"FileUsage"="0"

"Setup"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019S.DLL<file:///\\\servername\epicor\oe100b\bin\PGPRO1019S.DLL>"

"SQLLevel"="0"

"UsageCount"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]

"DataDirect 4.20 32-Bit Progress SQL92 v10.0B"="Installed"

5) Edit two lines of the text document to reflect your servers name. The
two lines are: "Driver ="

and "Setup=". Change the \\Servername<file:///\\Servername> to your servers actual name. Save
the changes.

6) Rename the ODBC.TXT doc to ODBC.REG. This will change the appearance
of the file and

allow it to be added to the registry.

7) Double click on the ODBC.REG file which will automatically import the
information into the

workstations registry.

Setup the ODBC DSN for the new DataDirect driver.

==========================================

8) Go to [Start] --> Settings --> Control Panel --> Administrative Tools
--> Data Sources

(ODBC)

9) Click on the [System] tab, then the [ADD] button.

10) Scroll down and locate the "DataDirect 4.20 32-Bit Progress SQL92
v10.0B" driver, hightlight

and click [FINISH].

11) Fill in the Properties window for the ODBC Progress OpenEdge Driver
Setup.

- Data Source Name: OpenEdge10B (do not use spaces in the name)

- Description: OpenEdge 10B

- Host Name: <enter your servers name here>

- Port Number: 8050 (for the Live database) 8060 (for the Training
database), 8070 (for test)

- Database Name: mfgsys

- User ID: sysprogress (or the name you have chosen and setup in your
6.x database.)

- Click on the Advanced tab and set the Default Isolation Level to Read
Uncommited

12) Click on [Apply] and then press [Test Connect]

13) Fill in the password, click [OK]. You should get "Connection
Established!". Click [OK]

USER NAME and PASSWORD Setup:

================================

NOTE If this is a new setup in that your database is either a new
install or has never been setup

to use ODBC, you will need to add an administrative user and password to
the database directly.

Follow the remaining steps below to setup user: "sysprogress" and a
password of your choice.

14) On the server or your Admin workstation if you have one setup, make
a copy of your

"SchemaChange" icon.

15) Rename the copied icon to "ODBC Setup".

16) Right mouse click the ODBC Setup icon and select "Properties".

17) On the ShortCut tab, Target line, change the last parameter on the
line from: applydf.w to

_admin.p Save the changes and double click.

18) In the Progress Database Administration utility, select ADMIN -->
SECURITY --> EDIT USER

LIST.

19) Click on [ADD], and fill in the following fields

- User ID: sysprogress

- User name: sysprogress

- Password: <this is your choice, do not forget what you entered>

20) Click [OK], and click [OK] again. Exit the Data Administration
session.

21) You should now be able to go back and "Test Connect" your DSN with
the User ID and

Password you just entered.

Note: if any problems with the registry entries, make sure you break it
up into lines

"key" = "Value"

________________________________

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf
Of Thomas Rose
Sent: Thursday, June 26, 2008 3:03 PM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Getting ODBC to work

I thought I was having some success getting ODBC to work for me. I am
finally able to see the database tables (after many failures), but I get
error messages now when I try to get data from the tables:
-When I try to link or import a table in Access I get the error message
"Reserved error (-7748); there is no message for this error."
-When I try to get data in a Crystal report, I get the error message
"Failed to retrieve data from the database. Details: HY000:
[DataDirect][ODBC Progress OpenEdge Wire Protocol
driver][OPENEDGE]Access denied (Authorization failed)(7512)[Database
Vendor Code: -20228 ]".

Any thoughts?

Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com/
<http://www.electricmirror.com/> >

[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]
The registry modification will work for all Access versions that I
have tried - 00,03,07. I am currently using 07.

I only needed to modify the CURRENT_USER node of the registry tree
and used a value of 40960 for my Workaround2 string.

In Access you will only have a SAVE PASSWORD box in the linked fields
process. The rest it is managed at the ODBC level.

If are successful with the Test Connection process via ODBC then that
username/password issue should be taken care of.

Also, it depends on what tables you are talking about. For example,
the customer table needs a view and many of the other tables need
special considerations as well through Access.

Ross

--- In vantage@yahoogroups.com, Thomas Rose <t.rose@...> wrote:
>
> Matt, Ross, and Vic,
>
> Thank you for your input. I am getting closer. Ross's advice
about the addition of WorkArounds2 to the registry, in particular,
seemed to get me closer. I tried with each of the values suggested.
I'm wondering, do those values apply to Access 2003 and Access 2000?
Is there another value that applies to Access 2007, the version I am
on?
>
> Vic, sorry about not supplying version number: 8.03.403D
>
> I have gotten far enough that I can see (in either Access or
Crystal) the tables in the database and the fields. I think your
answer primarily addresses those issues. I cannot see the data in
the tables, though. The one thing that your answer may be shedding
light on, though I am perhaps too dense to see, is a password issue.
If I use the user ID sysprogress, I do not have a valid password that
will even let me see the database. If I use the user ID and password
I use to log on normally, I can see the database, tables, and fields,
but not the data. Do I need to get the sysprogress password from my
administrator?
>
> Thank you for the help.
>
> Thom Rose
> Controller
> Electric Mirror, LLC
> T 425 776-4946 ext. 1024
> A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
> www.electricmirror.com<http://www.electricmirror.com/>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of Vic Drecchio
> Sent: Thursday, June 26, 2008 12:14 PM
> To: vantage@yahoogroups.com
> Cc: Thomas Rose
> Subject: {Disarmed} RE: [Vantage] Getting ODBC to work
>
>
> Tom, what version of Vantage? I'll assume 8.x.
>
> See if this helps you any: I also attached a more visual instruction
> sheet.
>
> Vic
>
> ++++++++++++++++++++++++++++++++++
> AnswerBook #: 7439MPS Product: Vantage
>
> Date Added: 10/30/2006 Version:
>
> Date Changed: 12/21/2006 Module: Installation
>
> Summary:
>
> 8.0 ODBC Setup - DataDirect 4.20 32-Bit Progress SQL92 v10.0B
>
> Details:
>
> PROBLEM DESCRIPTION: How to setup the ODBC Driver for MFGSYS version
> 8.0.
>
> PROBLEM RESOLUTION: Below are steps to setup the DataDirect 4.20 32-
Bit
> Progress SQL92
>
> v10.0B Driver for Mfgsys version 8.0.
>
> STEPS:
>
> 1) Using windows explorer, browse to your
server\epicor\oe100b\netsetup
> folder.
>
> 2) Double click on the SETUP.EXE in the netsetup folder which will
> install the "OpenEdge 10.B
>
> Shared Network Setup. For the working directory, you can point to
the
> shared folder on the
>
> server. (i.e. C:\epicor\mfgwrk80)
>
> 3) Create and open a new Text document at a workstation (i.e
ODBC.TXT).
>
> 4) Copy and paste all of the text below into that new (ODBC.TXT)
text
> doc.
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\DataDirect 4.20 32-
Bit
> Progress
>
> SQL92 v10.0B]
>
> "APILevel"="1"
>
> "ConnectFunctions"="YYN"
>
> "CPTimeout"="60"
>
> "Driver"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019.DLL<file://
/\\\servername\epicor\oe100b\bin\PGPRO1019.DLL>"
>
> "DriverODBCVer"="4.20"
>
> "FileUsage"="0"
>
> "Setup"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019S.DLL<file://
/\\\servername\epicor\oe100b\bin\PGPRO1019S.DLL>"
>
> "SQLLevel"="0"
>
> "UsageCount"="1"
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]
>
> "DataDirect 4.20 32-Bit Progress SQL92 v10.0B"="Installed"
>
> 5) Edit two lines of the text document to reflect your servers
name. The
> two lines are: "Driver ="
>
> and "Setup=". Change the \\Servername<file:///\\Servername> to your
servers actual name. Save
> the changes.
>
> 6) Rename the ODBC.TXT doc to ODBC.REG. This will change the
appearance
> of the file and
>
> allow it to be added to the registry.
>
> 7) Double click on the ODBC.REG file which will automatically
import the
> information into the
>
> workstations registry.
>
> Setup the ODBC DSN for the new DataDirect driver.
>
> ==========================================
>
> 8) Go to [Start] --> Settings --> Control Panel --> Administrative
Tools
> --> Data Sources
>
> (ODBC)
>
> 9) Click on the [System] tab, then the [ADD] button.
>
> 10) Scroll down and locate the "DataDirect 4.20 32-Bit Progress
SQL92
> v10.0B" driver, hightlight
>
> and click [FINISH].
>
> 11) Fill in the Properties window for the ODBC Progress OpenEdge
Driver
> Setup.
>
> - Data Source Name: OpenEdge10B (do not use spaces in the name)
>
> - Description: OpenEdge 10B
>
> - Host Name: <enter your servers name here>
>
> - Port Number: 8050 (for the Live database) 8060 (for the Training
> database), 8070 (for test)
>
> - Database Name: mfgsys
>
> - User ID: sysprogress (or the name you have chosen and setup in
your
> 6.x database.)
>
> - Click on the Advanced tab and set the Default Isolation Level to
Read
> Uncommited
>
> 12) Click on [Apply] and then press [Test Connect]
>
> 13) Fill in the password, click [OK]. You should get "Connection
> Established!". Click [OK]
>
> USER NAME and PASSWORD Setup:
>
> ================================
>
> NOTE If this is a new setup in that your database is either a new
> install or has never been setup
>
> to use ODBC, you will need to add an administrative user and
password to
> the database directly.
>
> Follow the remaining steps below to setup user: "sysprogress" and a
> password of your choice.
>
> 14) On the server or your Admin workstation if you have one setup,
make
> a copy of your
>
> "SchemaChange" icon.
>
> 15) Rename the copied icon to "ODBC Setup".
>
> 16) Right mouse click the ODBC Setup icon and select "Properties".
>
> 17) On the ShortCut tab, Target line, change the last parameter on
the
> line from: applydf.w to
>
> _admin.p Save the changes and double click.
>
> 18) In the Progress Database Administration utility, select ADMIN --
>
> SECURITY --> EDIT USER
>
> LIST.
>
> 19) Click on [ADD], and fill in the following fields
>
> - User ID: sysprogress
>
> - User name: sysprogress
>
> - Password: <this is your choice, do not forget what you entered>
>
> 20) Click [OK], and click [OK] again. Exit the Data Administration
> session.
>
> 21) You should now be able to go back and "Test Connect" your DSN
with
> the User ID and
>
> Password you just entered.
>
> Note: if any problems with the registry entries, make sure you
break it
> up into lines
>
> "key" = "Value"
>
> ________________________________
>
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On
Behalf
> Of Thomas Rose
> Sent: Thursday, June 26, 2008 3:03 PM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Getting ODBC to work
>
> I thought I was having some success getting ODBC to work for me. I
am
> finally able to see the database tables (after many failures), but
I get
> error messages now when I try to get data from the tables:
> -When I try to link or import a table in Access I get the error
message
> "Reserved error (-7748); there is no message for this error."
> -When I try to get data in a Crystal report, I get the error message
> "Failed to retrieve data from the database. Details: HY000:
> [DataDirect][ODBC Progress OpenEdge Wire Protocol
> driver][OPENEDGE]Access denied (Authorization failed)(7512)[Database
> Vendor Code: -20228 ]".
>
> Any thoughts?
>
> Thom Rose
> Controller
> Electric Mirror, LLC
> T 425 776-4946 ext. 1024
> A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
> www.electricmirror.com<http://www.electricmirror.com/
> <http://www.electricmirror.com/> >
>
> [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 feel like I am working on a jigsaw puzzle. I have all the pieces turned picture side up and now I just have to put it all together.

Your last paragraph is something I'm trying to take in, and seems to raise more questions:

- Where are the views?

- Which tables have views?

- Are there any tables I can access directly?

- What are the "special considerations" needed for the other tables?

I apologize for sounding completely dense about this subject. I am used to linking SQL Server tables using ODBC into Access databases and, so far, that is a lot easier. Of course, if I think about it long enough, I will probably realize it took me just as long to get up to speed on that use of ODBC.

In any case, I do appreciate everyone's help so far!

Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Ross Hughes
Sent: Thursday, June 26, 2008 2:18 PM
To: vantage@yahoogroups.com
Subject: {Disarmed} [Vantage] Re: Getting ODBC to work


The registry modification will work for all Access versions that I
have tried - 00,03,07. I am currently using 07.

I only needed to modify the CURRENT_USER node of the registry tree
and used a value of 40960 for my Workaround2 string.

In Access you will only have a SAVE PASSWORD box in the linked fields
process. The rest it is managed at the ODBC level.

If are successful with the Test Connection process via ODBC then that
username/password issue should be taken care of.

Also, it depends on what tables you are talking about. For example,
the customer table needs a view and many of the other tables need
special considerations as well through Access.

Ross

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Thomas Rose <t.rose@...> wrote:
>
> Matt, Ross, and Vic,
>
> Thank you for your input. I am getting closer. Ross's advice
about the addition of WorkArounds2 to the registry, in particular,
seemed to get me closer. I tried with each of the values suggested.
I'm wondering, do those values apply to Access 2003 and Access 2000?
Is there another value that applies to Access 2007, the version I am
on?
>
> Vic, sorry about not supplying version number: 8.03.403D
>
> I have gotten far enough that I can see (in either Access or
Crystal) the tables in the database and the fields. I think your
answer primarily addresses those issues. I cannot see the data in
the tables, though. The one thing that your answer may be shedding
light on, though I am perhaps too dense to see, is a password issue.
If I use the user ID sysprogress, I do not have a valid password that
will even let me see the database. If I use the user ID and password
I use to log on normally, I can see the database, tables, and fields,
but not the data. Do I need to get the sysprogress password from my
administrator?
>
> Thank you for the help.
>
> Thom Rose
> Controller
> Electric Mirror, LLC
> T 425 776-4946 ext. 1024
> A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
> www.electricmirror.com<http://www.electricmirror.com/>
>
> From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On
Behalf Of Vic Drecchio
> Sent: Thursday, June 26, 2008 12:14 PM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> Cc: Thomas Rose
> Subject: {Disarmed} RE: [Vantage] Getting ODBC to work
>
>
> Tom, what version of Vantage? I'll assume 8.x.
>
> See if this helps you any: I also attached a more visual instruction
> sheet.
>
> Vic
>
> ++++++++++++++++++++++++++++++++++
> AnswerBook #: 7439MPS Product: Vantage
>
> Date Added: 10/30/2006 Version:
>
> Date Changed: 12/21/2006 Module: Installation
>
> Summary:
>
> 8.0 ODBC Setup - DataDirect 4.20 32-Bit Progress SQL92 v10.0B
>
> Details:
>
> PROBLEM DESCRIPTION: How to setup the ODBC Driver for MFGSYS version
> 8.0.
>
> PROBLEM RESOLUTION: Below are steps to setup the DataDirect 4.20 32-
Bit
> Progress SQL92
>
> v10.0B Driver for Mfgsys version 8.0.
>
> STEPS:
>
> 1) Using windows explorer, browse to your
server\epicor\oe100b\netsetup
> folder.
>
> 2) Double click on the SETUP.EXE in the netsetup folder which will
> install the "OpenEdge 10.B
>
> Shared Network Setup. For the working directory, you can point to
the
> shared folder on the
>
> server. (i.e. C:\epicor\mfgwrk80)
>
> 3) Create and open a new Text document at a workstation (i.e
ODBC.TXT).
>
> 4) Copy and paste all of the text below into that new (ODBC.TXT)
text
> doc.
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\DataDirect 4.20 32-
Bit
> Progress
>
> SQL92 v10.0B]
>
> "APILevel"="1"
>
> "ConnectFunctions"="YYN"
>
> "CPTimeout"="60"
>
> "Driver"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019.DLL<file://
/\\\servername\epicor\oe100b\bin\PGPRO1019.DLL>"
>
> "DriverODBCVer"="4.20"
>
> "FileUsage"="0"
>
> "Setup"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019S.DLL<file://
/\\\servername\epicor\oe100b\bin\PGPRO1019S.DLL>"
>
> "SQLLevel"="0"
>
> "UsageCount"="1"
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]
>
> "DataDirect 4.20 32-Bit Progress SQL92 v10.0B"="Installed"
>
> 5) Edit two lines of the text document to reflect your servers
name. The
> two lines are: "Driver ="
>
> and "Setup=". Change the \\Servername<file:///<file:///\\>\\Servername> to your
servers actual name. Save
> the changes.
>
> 6) Rename the ODBC.TXT doc to ODBC.REG. This will change the
appearance
> of the file and
>
> allow it to be added to the registry.
>
> 7) Double click on the ODBC.REG file which will automatically
import the
> information into the
>
> workstations registry.
>
> Setup the ODBC DSN for the new DataDirect driver.
>
> ==========================================
>
> 8) Go to [Start] --> Settings --> Control Panel --> Administrative
Tools
> --> Data Sources
>
> (ODBC)
>
> 9) Click on the [System] tab, then the [ADD] button.
>
> 10) Scroll down and locate the "DataDirect 4.20 32-Bit Progress
SQL92
> v10.0B" driver, hightlight
>
> and click [FINISH].
>
> 11) Fill in the Properties window for the ODBC Progress OpenEdge
Driver
> Setup.
>
> - Data Source Name: OpenEdge10B (do not use spaces in the name)
>
> - Description: OpenEdge 10B
>
> - Host Name: <enter your servers name here>
>
> - Port Number: 8050 (for the Live database) 8060 (for the Training
> database), 8070 (for test)
>
> - Database Name: mfgsys
>
> - User ID: sysprogress (or the name you have chosen and setup in
your
> 6.x database.)
>
> - Click on the Advanced tab and set the Default Isolation Level to
Read
> Uncommited
>
> 12) Click on [Apply] and then press [Test Connect]
>
> 13) Fill in the password, click [OK]. You should get "Connection
> Established!". Click [OK]
>
> USER NAME and PASSWORD Setup:
>
> ================================
>
> NOTE If this is a new setup in that your database is either a new
> install or has never been setup
>
> to use ODBC, you will need to add an administrative user and
password to
> the database directly.
>
> Follow the remaining steps below to setup user: "sysprogress" and a
> password of your choice.
>
> 14) On the server or your Admin workstation if you have one setup,
make
> a copy of your
>
> "SchemaChange" icon.
>
> 15) Rename the copied icon to "ODBC Setup".
>
> 16) Right mouse click the ODBC Setup icon and select "Properties".
>
> 17) On the ShortCut tab, Target line, change the last parameter on
the
> line from: applydf.w to
>
> _admin.p Save the changes and double click.
>
> 18) In the Progress Database Administration utility, select ADMIN --
>
> SECURITY --> EDIT USER
>
> LIST.
>
> 19) Click on [ADD], and fill in the following fields
>
> - User ID: sysprogress
>
> - User name: sysprogress
>
> - Password: <this is your choice, do not forget what you entered>
>
> 20) Click [OK], and click [OK] again. Exit the Data Administration
> session.
>
> 21) You should now be able to go back and "Test Connect" your DSN
with
> the User ID and
>
> Password you just entered.
>
> Note: if any problems with the registry entries, make sure you
break it
> up into lines
>
> "key" = "Value"
>
> ________________________________
>
> 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 Thomas Rose
> Sent: Thursday, June 26, 2008 3:03 PM
> To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Getting ODBC to work
>
> I thought I was having some success getting ODBC to work for me. I
am
> finally able to see the database tables (after many failures), but
I get
> error messages now when I try to get data from the tables:
> -When I try to link or import a table in Access I get the error
message
> "Reserved error (-7748); there is no message for this error."
> -When I try to get data in a Crystal report, I get the error message
> "Failed to retrieve data from the database. Details: HY000:
> [DataDirect][ODBC Progress OpenEdge Wire Protocol
> driver][OPENEDGE]Access denied (Authorization failed)(7512)[Database
> Vendor Code: -20228 ]".
>
> Any thoughts?
>
> Thom Rose
> Controller
> Electric Mirror, LLC
> T 425 776-4946 ext. 1024
> A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
> www.electricmirror.com<http://www.electricmirror.com/
> <http://www.electricmirror.com/> >
>
> [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]
Views are SQL views that are basically queries that wrap over the table.
These are required to read some tables because they have multiple indexes in
Progress and Access wants them to have one.



Customer table needs a view. It seems like there is one with Jobs, I can't
remember which one right now.maybe JobOper. You will get the error about
'too many indexes' and have to create a view.



Most of the tables you can access directly.some just need adjustment.



The special considerations are me saying this is kind of clunky and yet
works. You will get field length errors on some tables. If that happens
you need to go to the Progress db administration tool and change the lengths
of the fields. There are instructions for this when you run across this.



I also run in to the data in a table only presenting itself until you start
to scroll through the table.then it all turns to # signs. The only way I
can consistently return the data in these situations is with a Access query
wrapped around it..especially when I am filtering something off.



All and all, I am a big fan of using Access as an all-purpose tool. It is
so flexible and easy to access things once you get it connected.



Ross



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Thomas Rose
Sent: Friday, June 27, 2008 5:16 PM
To: vantage@yahoogroups.com
Subject: RE: {Disarmed} [Vantage] Re: Getting ODBC to work



I feel like I am working on a jigsaw puzzle. I have all the pieces turned
picture side up and now I just have to put it all together.

Your last paragraph is something I'm trying to take in, and seems to raise
more questions:

- Where are the views?

- Which tables have views?

- Are there any tables I can access directly?

- What are the "special considerations" needed for the other tables?

I apologize for sounding completely dense about this subject. I am used to
linking SQL Server tables using ODBC into Access databases and, so far, that
is a lot easier. Of course, if I think about it long enough, I will probably
realize it took me just as long to get up to speed on that use of ODBC.

In any case, I do appreciate everyone's help so far!

Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electricmirror.com/>

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of Ross Hughes
Sent: Thursday, June 26, 2008 2:18 PM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: {Disarmed} [Vantage] Re: Getting ODBC to work

The registry modification will work for all Access versions that I
have tried - 00,03,07. I am currently using 07.

I only needed to modify the CURRENT_USER node of the registry tree
and used a value of 40960 for my Workaround2 string.

In Access you will only have a SAVE PASSWORD box in the linked fields
process. The rest it is managed at the ODBC level.

If are successful with the Test Connection process via ODBC then that
username/password issue should be taken care of.

Also, it depends on what tables you are talking about. For example,
the customer table needs a view and many of the other tables need
special considerations as well through Access.

Ross

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>, Thomas Rose <t.rose@...> wrote:
>
> Matt, Ross, and Vic,
>
> Thank you for your input. I am getting closer. Ross's advice
about the addition of WorkArounds2 to the registry, in particular,
seemed to get me closer. I tried with each of the values suggested.
I'm wondering, do those values apply to Access 2003 and Access 2000?
Is there another value that applies to Access 2007, the version I am
on?
>
> Vic, sorry about not supplying version number: 8.03.403D
>
> I have gotten far enough that I can see (in either Access or
Crystal) the tables in the database and the fields. I think your
answer primarily addresses those issues. I cannot see the data in
the tables, though. The one thing that your answer may be shedding
light on, though I am perhaps too dense to see, is a password issue.
If I use the user ID sysprogress, I do not have a valid password that
will even let me see the database. If I use the user ID and password
I use to log on normally, I can see the database, tables, and fields,
but not the data. Do I need to get the sysprogress password from my
administrator?
>
> Thank you for the help.
>
> Thom Rose
> Controller
> Electric Mirror, LLC
> T 425 776-4946 ext. 1024
> A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
> www.electricmirror.com<http://www.electricmirror.com/>
>
> 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 Vic Drecchio
> Sent: Thursday, June 26, 2008 12:14 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
> Cc: Thomas Rose
> Subject: {Disarmed} RE: [Vantage] Getting ODBC to work
>
>
> Tom, what version of Vantage? I'll assume 8.x.
>
> See if this helps you any: I also attached a more visual instruction
> sheet.
>
> Vic
>
> ++++++++++++++++++++++++++++++++++
> AnswerBook #: 7439MPS Product: Vantage
>
> Date Added: 10/30/2006 Version:
>
> Date Changed: 12/21/2006 Module: Installation
>
> Summary:
>
> 8.0 ODBC Setup - DataDirect 4.20 32-Bit Progress SQL92 v10.0B
>
> Details:
>
> PROBLEM DESCRIPTION: How to setup the ODBC Driver for MFGSYS version
> 8.0.
>
> PROBLEM RESOLUTION: Below are steps to setup the DataDirect 4.20 32-
Bit
> Progress SQL92
>
> v10.0B Driver for Mfgsys version 8.0.
>
> STEPS:
>
> 1) Using windows explorer, browse to your
server\epicor\oe100b\netsetup
> folder.
>
> 2) Double click on the SETUP.EXE in the netsetup folder which will
> install the "OpenEdge 10.B
>
> Shared Network Setup. For the working directory, you can point to
the
> shared folder on the
>
> server. (i.e. C:\epicor\mfgwrk80)
>
> 3) Create and open a new Text document at a workstation (i.e
ODBC.TXT).
>
> 4) Copy and paste all of the text below into that new (ODBC.TXT)
text
> doc.
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\DataDirect 4.20 32-
Bit
> Progress
>
> SQL92 v10.0B]
>
> "APILevel"="1"
>
> "ConnectFunctions"="YYN"
>
> "CPTimeout"="60"
>
> "Driver"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019.DLL<file://
/\\\servername\epicor\oe100b\bin\PGPRO1019.DLL>"
>
> "DriverODBCVer"="4.20"
>
> "FileUsage"="0"
>
> "Setup"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019S.DLL<file://
/\\\servername\epicor\oe100b\bin\PGPRO1019S.DLL>"
>
> "SQLLevel"="0"
>
> "UsageCount"="1"
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]
>
> "DataDirect 4.20 32-Bit Progress SQL92 v10.0B"="Installed"
>
> 5) Edit two lines of the text document to reflect your servers
name. The
> two lines are: "Driver ="
>
> and "Setup=". Change the \\Servername<file:/// <file:///\\> <file:///
<file:///\\> \\>\\Servername> to your
servers actual name. Save
> the changes.
>
> 6) Rename the ODBC.TXT doc to ODBC.REG. This will change the
appearance
> of the file and
>
> allow it to be added to the registry.
>
> 7) Double click on the ODBC.REG file which will automatically
import the
> information into the
>
> workstations registry.
>
> Setup the ODBC DSN for the new DataDirect driver.
>
> ==========================================
>
> 8) Go to [Start] --> Settings --> Control Panel --> Administrative
Tools
> --> Data Sources
>
> (ODBC)
>
> 9) Click on the [System] tab, then the [ADD] button.
>
> 10) Scroll down and locate the "DataDirect 4.20 32-Bit Progress
SQL92
> v10.0B" driver, hightlight
>
> and click [FINISH].
>
> 11) Fill in the Properties window for the ODBC Progress OpenEdge
Driver
> Setup.
>
> - Data Source Name: OpenEdge10B (do not use spaces in the name)
>
> - Description: OpenEdge 10B
>
> - Host Name: <enter your servers name here>
>
> - Port Number: 8050 (for the Live database) 8060 (for the Training
> database), 8070 (for test)
>
> - Database Name: mfgsys
>
> - User ID: sysprogress (or the name you have chosen and setup in
your
> 6.x database.)
>
> - Click on the Advanced tab and set the Default Isolation Level to
Read
> Uncommited
>
> 12) Click on [Apply] and then press [Test Connect]
>
> 13) Fill in the password, click [OK]. You should get "Connection
> Established!". Click [OK]
>
> USER NAME and PASSWORD Setup:
>
> ================================
>
> NOTE If this is a new setup in that your database is either a new
> install or has never been setup
>
> to use ODBC, you will need to add an administrative user and
password to
> the database directly.
>
> Follow the remaining steps below to setup user: "sysprogress" and a
> password of your choice.
>
> 14) On the server or your Admin workstation if you have one setup,
make
> a copy of your
>
> "SchemaChange" icon.
>
> 15) Rename the copied icon to "ODBC Setup".
>
> 16) Right mouse click the ODBC Setup icon and select "Properties".
>
> 17) On the ShortCut tab, Target line, change the last parameter on
the
> line from: applydf.w to
>
> _admin.p Save the changes and double click.
>
> 18) In the Progress Database Administration utility, select ADMIN --
>
> SECURITY --> EDIT USER
>
> LIST.
>
> 19) Click on [ADD], and fill in the following fields
>
> - User ID: sysprogress
>
> - User name: sysprogress
>
> - Password: <this is your choice, do not forget what you entered>
>
> 20) Click [OK], and click [OK] again. Exit the Data Administration
> session.
>
> 21) You should now be able to go back and "Test Connect" your DSN
with
> the User ID and
>
> Password you just entered.
>
> Note: if any problems with the registry entries, make sure you
break it
> up into lines
>
> "key" = "Value"
>
> ________________________________
>
> 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 Thomas Rose
> Sent: Thursday, June 26, 2008 3:03 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Getting ODBC to work
>
> I thought I was having some success getting ODBC to work for me. I
am
> finally able to see the database tables (after many failures), but
I get
> error messages now when I try to get data from the tables:
> -When I try to link or import a table in Access I get the error
message
> "Reserved error (-7748); there is no message for this error."
> -When I try to get data in a Crystal report, I get the error message
> "Failed to retrieve data from the database. Details: HY000:
> [DataDirect][ODBC Progress OpenEdge Wire Protocol
> driver][OPENEDGE]Access denied (Authorization failed)(7512)[Database
> Vendor Code: -20228 ]".
>
> Any thoughts?
>
> Thom Rose
> Controller
> Electric Mirror, LLC
> T 425 776-4946 ext. 1024
> A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
> www.electricmirror.com<http://www.electricmirror.com/
> <http://www.electricmirror.com/> >
>
> [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]





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



Is the return of the ### on scrolling not just because more fields have been
returned than access can handle, I presume you query limits the result some
way? I was having the same issue when I tried cccess and msquery on the
change log and the only way to get a result was to limit the number of
records returned by the query, my end solution was just to use a query from
VB as this does not have the same restrictions.



Tim Stevenson



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Ross Hughes
Sent: Sunday, 29 June 2008 12:15 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Getting ODBC to work



Views are SQL views that are basically queries that wrap over the table.
These are required to read some tables because they have multiple indexes in
Progress and Access wants them to have one.

Customer table needs a view. It seems like there is one with Jobs, I can't
remember which one right now.maybe JobOper. You will get the error about
'too many indexes' and have to create a view.

Most of the tables you can access directly.some just need adjustment.

The special considerations are me saying this is kind of clunky and yet
works. You will get field length errors on some tables. If that happens
you need to go to the Progress db administration tool and change the lengths
of the fields. There are instructions for this when you run across this.

I also run in to the data in a table only presenting itself until you start
to scroll through the table.then it all turns to # signs. The only way I
can consistently return the data in these situations is with a Access query
wrapped around it..especially when I am filtering something off.

All and all, I am a big fan of using Access as an all-purpose tool. It is
so flexible and easy to access things once you get it connected.

Ross

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
Behalf Of
Thomas Rose
Sent: Friday, June 27, 2008 5:16 PM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Subject: RE: {Disarmed} [Vantage] Re: Getting ODBC to work

I feel like I am working on a jigsaw puzzle. I have all the pieces turned
picture side up and now I just have to put it all together.

Your last paragraph is something I'm trying to take in, and seems to raise
more questions:

- Where are the views?

- Which tables have views?

- Are there any tables I can access directly?

- What are the "special considerations" needed for the other tables?

I apologize for sounding completely dense about this subject. I am used to
linking SQL Server tables using ODBC into Access databases and, so far, that
is a lot easier. Of course, if I think about it long enough, I will probably
realize it took me just as long to get up to speed on that use of ODBC.

In any case, I do appreciate everyone's help so far!

Thom Rose
Controller
Electric Mirror, LLC
T 425 776-4946 ext. 1024
A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
www.electricmirror.com<http://www.electric <http://www.electricmirror.com/>
mirror.com/>

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com> ] On
Behalf Of Ross Hughes
Sent: Thursday, June 26, 2008 2:18 PM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
Subject: {Disarmed} [Vantage] Re: Getting ODBC to work

The registry modification will work for all Access versions that I
have tried - 00,03,07. I am currently using 07.

I only needed to modify the CURRENT_USER node of the registry tree
and used a value of 40960 for my Workaround2 string.

In Access you will only have a SAVE PASSWORD box in the linked fields
process. The rest it is managed at the ODBC level.

If are successful with the Test Connection process via ODBC then that
username/password issue should be taken care of.

Also, it depends on what tables you are talking about. For example,
the customer table needs a view and many of the other tables need
special considerations as well through Access.

Ross

--- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>, Thomas Rose <t.rose@...> wrote:
>
> Matt, Ross, and Vic,
>
> Thank you for your input. I am getting closer. Ross's advice
about the addition of WorkArounds2 to the registry, in particular,
seemed to get me closer. I tried with each of the values suggested.
I'm wondering, do those values apply to Access 2003 and Access 2000?
Is there another value that applies to Access 2007, the version I am
on?
>
> Vic, sorry about not supplying version number: 8.03.403D
>
> I have gotten far enough that I can see (in either Access or
Crystal) the tables in the database and the fields. I think your
answer primarily addresses those issues. I cannot see the data in
the tables, though. The one thing that your answer may be shedding
light on, though I am perhaps too dense to see, is a password issue.
If I use the user ID sysprogress, I do not have a valid password that
will even let me see the database. If I use the user ID and password
I use to log on normally, I can see the database, tables, and fields,
but not the data. Do I need to get the sysprogress password from my
administrator?
>
> Thank you for the help.
>
> Thom Rose
> Controller
> Electric Mirror, LLC
> T 425 776-4946 ext. 1024
> A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
> www.electricmirror.com<http://www.electric
<http://www.electricmirror.com/> mirror.com/>
>
> From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups
<mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>] On
Behalf Of Vic Drecchio
> Sent: Thursday, June 26, 2008 12:14 PM
> To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
> Cc: Thomas Rose
> Subject: {Disarmed} RE: [Vantage] Getting ODBC to work
>
>
> Tom, what version of Vantage? I'll assume 8.x.
>
> See if this helps you any: I also attached a more visual instruction
> sheet.
>
> Vic
>
> ++++++++++++++++++++++++++++++++++
> AnswerBook #: 7439MPS Product: Vantage
>
> Date Added: 10/30/2006 Version:
>
> Date Changed: 12/21/2006 Module: Installation
>
> Summary:
>
> 8.0 ODBC Setup - DataDirect 4.20 32-Bit Progress SQL92 v10.0B
>
> Details:
>
> PROBLEM DESCRIPTION: How to setup the ODBC Driver for MFGSYS version
> 8.0.
>
> PROBLEM RESOLUTION: Below are steps to setup the DataDirect 4.20 32-
Bit
> Progress SQL92
>
> v10.0B Driver for Mfgsys version 8.0.
>
> STEPS:
>
> 1) Using windows explorer, browse to your
server\epicor\oe100b\netsetup
> folder.
>
> 2) Double click on the SETUP.EXE in the netsetup folder which will
> install the "OpenEdge 10.B
>
> Shared Network Setup. For the working directory, you can point to
the
> shared folder on the
>
> server. (i.e. C:\epicor\mfgwrk80)
>
> 3) Create and open a new Text document at a workstation (i.e
ODBC.TXT).
>
> 4) Copy and paste all of the text below into that new (ODBC.TXT)
text
> doc.
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\DataDirect 4.20 32-
Bit
> Progress
>
> SQL92 v10.0B]
>
> "APILevel"="1"
>
> "ConnectFunctions"="YYN"
>
> "CPTimeout"="60"
>
> "Driver"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019.DLL<file://
/\\\servername\epicor\oe100b\bin\PGPRO1019.DLL>"
>
> "DriverODBCVer"="4.20"
>
> "FileUsage"="0"
>
> "Setup"="\\\\servername\\epicor\\oe100b\\bin\\PGPRO1019S.DLL<file://
/\\\servername\epicor\oe100b\bin\PGPRO1019S.DLL>"
>
> "SQLLevel"="0"
>
> "UsageCount"="1"
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]
>
> "DataDirect 4.20 32-Bit Progress SQL92 v10.0B"="Installed"
>
> 5) Edit two lines of the text document to reflect your servers
name. The
> two lines are: "Driver ="
>
> and "Setup=". Change the \\Servername<file:/// <file:///\\> <file:///
<file:///\\> \\> <file:/// <file:///\\>
<file:/// <file:///\\> \\> \\>\\Servername> to your
servers actual name. Save
> the changes.
>
> 6) Rename the ODBC.TXT doc to ODBC.REG. This will change the
appearance
> of the file and
>
> allow it to be added to the registry.
>
> 7) Double click on the ODBC.REG file which will automatically
import the
> information into the
>
> workstations registry.
>
> Setup the ODBC DSN for the new DataDirect driver.
>
> ==========================================
>
> 8) Go to [Start] --> Settings --> Control Panel --> Administrative
Tools
> --> Data Sources
>
> (ODBC)
>
> 9) Click on the [System] tab, then the [ADD] button.
>
> 10) Scroll down and locate the "DataDirect 4.20 32-Bit Progress
SQL92
> v10.0B" driver, hightlight
>
> and click [FINISH].
>
> 11) Fill in the Properties window for the ODBC Progress OpenEdge
Driver
> Setup.
>
> - Data Source Name: OpenEdge10B (do not use spaces in the name)
>
> - Description: OpenEdge 10B
>
> - Host Name: <enter your servers name here>
>
> - Port Number: 8050 (for the Live database) 8060 (for the Training
> database), 8070 (for test)
>
> - Database Name: mfgsys
>
> - User ID: sysprogress (or the name you have chosen and setup in
your
> 6.x database.)
>
> - Click on the Advanced tab and set the Default Isolation Level to
Read
> Uncommited
>
> 12) Click on [Apply] and then press [Test Connect]
>
> 13) Fill in the password, click [OK]. You should get "Connection
> Established!". Click [OK]
>
> USER NAME and PASSWORD Setup:
>
> ================================
>
> NOTE If this is a new setup in that your database is either a new
> install or has never been setup
>
> to use ODBC, you will need to add an administrative user and
password to
> the database directly.
>
> Follow the remaining steps below to setup user: "sysprogress" and a
> password of your choice.
>
> 14) On the server or your Admin workstation if you have one setup,
make
> a copy of your
>
> "SchemaChange" icon.
>
> 15) Rename the copied icon to "ODBC Setup".
>
> 16) Right mouse click the ODBC Setup icon and select "Properties".
>
> 17) On the ShortCut tab, Target line, change the last parameter on
the
> line from: applydf.w to
>
> _admin.p Save the changes and double click.
>
> 18) In the Progress Database Administration utility, select ADMIN --
>
> SECURITY --> EDIT USER
>
> LIST.
>
> 19) Click on [ADD], and fill in the following fields
>
> - User ID: sysprogress
>
> - User name: sysprogress
>
> - Password: <this is your choice, do not forget what you entered>
>
> 20) Click [OK], and click [OK] again. Exit the Data Administration
> session.
>
> 21) You should now be able to go back and "Test Connect" your DSN
with
> the User ID and
>
> Password you just entered.
>
> Note: if any problems with the registry entries, make sure you
break it
> up into lines
>
> "key" = "Value"
>
> ________________________________
>
> From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>] On
Behalf
> Of Thomas Rose
> Sent: Thursday, June 26, 2008 3:03 PM
> To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
<mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Getting ODBC to work
>
> I thought I was having some success getting ODBC to work for me. I
am
> finally able to see the database tables (after many failures), but
I get
> error messages now when I try to get data from the tables:
> -When I try to link or import a table in Access I get the error
message
> "Reserved error (-7748); there is no message for this error."
> -When I try to get data in a Crystal report, I get the error message
> "Failed to retrieve data from the database. Details: HY000:
> [DataDirect][ODBC Progress OpenEdge Wire Protocol
> driver][OPENEDGE]Access denied (Authorization failed)(7512)[Database
> Vendor Code: -20228 ]".
>
> Any thoughts?
>
> Thom Rose
> Controller
> Electric Mirror, LLC
> T 425 776-4946 ext. 1024
> A 11831 Beverly Park Road, Building D, Everett, WA 98204 USA
> www.electricmirror.com<http://www.electric
<http://www.electricmirror.com/> mirror.com/
> <http://www.electric <http://www.electricmirror.com/> mirror.com/> >
>
> [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]

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





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