ODBC access in 8.03.403d

Yahoo Archive
1
That worked. Thanks loads.


-- In vantage@yahoogroups.com, "Dave Olender" <dolender@...> wrote:
>
> Mr. Charles: I ran into the same error using my Vista 64bit and
found
> the following on the Progress site. Add the registry key
> Workarounds2=40696 to fix this.
>
> ID: P116845
> Title: "Reserved error -7748 when attempting to link a OpenEdge
10.1x
> Database table in Microsoft Access"
>
> Created: 06/20/2006 Last Modified: 09/24/2007
> Status: Unverified
>
> Facts:
>
> OpenEdge 10.1A
> OpenEdge 10.1B
> Progress OpenEdge 10.1A driver
> Progress OpenEdge 10.1B driver
> Windows
>
>
>
> Symptoms:
>
> Error attempting to link a OpenEdge Database table in MS Access
> Reserved error (-7748): there is no message for this error
> Error in ODBC trace file
> DIAG [01004] [DataDirect][ODBC Progress OpenEdge Wire Protocol
driver]
> String data, right truncated. Error in column 10. (0)
> Problem occurs when using the 5.1 DataDirect driver shipped with
10.1A
> Problem occurs when using the 5.1 DataDirect driver shipped with
10.1B
> Problem does not occur with the 4.2 DataDirect driver shipped with
10.0B
>
>
>
>
> Cause:
> Known issue with the DataDirect driver
>
>
> Fixes:
>
> WARNING - You should always make a backup of the Registry before
any
> changes.
>
> 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 (The string value that must be
added
> to Windows XP SP2 and Progress 10.1A02 is WorkArounds2=40960)
>
> 7. Click OK
>
> 8. Close RegEdit
>
> PCs running Windows 95 and 98 need to be rebooted for this setting
to
> take effect
>
> 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. Thus,
> the driver returns a warning, "01004 Data truncated", and returns a
> null character to Microsoft Access. Microsoft Access then passes
> error -7748. Setting this workaround causes Microsoft Access to not
> pass the error -7748.
>
>
> Good Luck,
>
> Dave Olender dolender@...
> Ph: 651-246-3281
>
>
> --- In vantage@yahoogroups.com, "charles06072006" <shadow031449@>
> wrote:
> >
> > I have been trying to add a link table to an access database with
the
> > new Progress OpenEdge 10.1B ODBC driver for 8.03.403d. Every time
I
> > make the attempt I get this error message:
> >
> > Reserved error (-7748); there is no message for this error.
> >
> > I have existing link tables in the access database and they work
fine.
> > I just can't set up a new link. If I delete a current linked
table I
> > am also not able to relink it. I have tried this in Windows Vista
> > (32bit) with Office 2007 and in Windows XP (32bit) with Office
2003.
> > Same message both places.
> >
> > Anyone have any ideas?
> >
>
2
I have been trying to add a link table to an access database with the
new Progress OpenEdge 10.1B ODBC driver for 8.03.403d. Every time I
make the attempt I get this error message:

Reserved error (-7748); there is no message for this error.

I have existing link tables in the access database and they work fine.
I just can't set up a new link. If I delete a current linked table I
am also not able to relink it. I have tried this in Windows Vista
(32bit) with Office 2007 and in Windows XP (32bit) with Office 2003.
Same message both places.

Anyone have any ideas?
3
We are running into a slight problem here.



We have searched for answers and now it's time to ask for some other help.



This is from one of the other techs I work with.



Hi,



I'm running into trouble using engineered parts in our live database.
Everything works fine in the "training" database, but when I try to use it
in "live" or "test" (a recent backup of "live"), it just doesn't seem to
work.



When I create a job to make an engineered part, the Job Manager does not
show any of the assembly details (operations, materials, etc). In fact, the
"Get Details" menu option is grayed out. This only happens when using the
live/test databases, training behaves perfectly.



Thinking that it must just be something that's configured differently
between the two databases, I created identical parts, operations, resources,
customers, etc but nothing seems to make a difference. I'm guessing that
it's still some setting that's different between the two databases, but I'm
not sure where to look. Any ideas?



Thanks in advance,



Jeff







Here are the steps I've followed in both "Test" and "Training" to create
identical test parts, operations, resources, and customers.





Run Part Maintenance



=== Create test-p1 part ===



click "New" icon

Enter part ID as "test-p1"

Enter description and set type to "Purchased".

All other options are left as default ("Use Part Rev", and "Quantity
Bearing" are checked, all others unchecked)

click "Save"





=== Create test-m1 part ===



Click the "new" icon

Enter Part ID as "test-m1"

Enter description and set type to "Manufactured".

Check "Non-Stock Item", all others are left as default ("Use Part Rev", and
"Quantity Bearing" are checked, all others unchecked)



Click the arrow next to the "new" icon, choose "New Part Revision"

Name the revision "A", enter description



On the menu select Actions|Revision|Check Out Revision



On the "Part Revision Checkout" screen

Click "New ECO"

"ECO Group Maintenance"

enter "TEST" as Group ID, description, and ECO, click OK

back on "Checkout", click OK



from the menu, choose Actions|Revision|Engineering Workbench



On the "Engineering Workbench"

Actions|Operation|Add Operation

Right click on the "Operation" dropdown, select Open with|Operation Entry



"Operation Maintenance"

Create new operation "TEST", enter description, type "Manufacturing",
all other options unchecked or blank

On the toolbar, click the dropdown next to the "new icon", choose "New
Resource Group Requirement"

Right click on the "ResourceGrpID" cell, select Open with|Resource Group
Entry



"Resource Group Maintenance"

Click the new icon

enter "TEST" as the group ID, enter a description.

Right click on "Department", choose Open With|JC Department Entry



"Job Department Maintenance"

Enter "TEST" as the Job Dept ID, enter a description, leave "GL
Division" and "GL Department" blank

click save, close the "Job Department Maintenance" window



Back on "Resource Group Maintenance", select "Test" as the department,
leave all other options as defaults

Click the arrow next to the new icon, choose "New Resource"

Enter "TEST" as the ResourceID, enter a description, leave all other
options as default

Click save, close "Resource Group Maintenance"



Back on "Operation Maintenance", enter "TEST" as the ResourceGroupID

Click save, close "Operation Maintenance"



Back on "Engineering Workbench", enter "TEST" as the operation

From the menu, choose Actions|Material|Add Material

Enter "test-p1" as the part ID

Enter quantity as "1", leave all other options as default

Click the revision tab, check "Approved"

from the menu, choose Actions|Revision|Check In

leave the default description of change, click "OK"



Back on part maintenance, click save and close part maintenance







=== Create new Order ===



Open Order Entry



Click the "New" icon

Right click on the "ID" field, choose Open With|Customer Entry



"Customer Maintenance"

Click the "New" icon

Enter "TEST" as ID and description, change "Type" to "Customer"

Click, the "Billing" tab, click the "Credit" subtab, uncheck "Credit Hold"

leave all else as default, click ok

click save, close Customer Maintenance



Click the dropdown next to the New icon, choose "New Line"

under line detail, enter "test-m2" as the part, "Selling Quantity" as 1,
Need by Date to "2/22/2022" and check "Create Job"

click Save

click the "Create Jobs" button

Click the "Releases tab"

Right click on the Job Id, and choose Open With|Job Entry



"Job Entry"

from the menu, choose Actions|Job|Get Details <================= THIS IS
GREYED OUT, WHY?













-Allen R. Bernstein

Sales/Network Tech

TCB Networks

(269) 385-8180





[Non-text portions of this message have been removed]
4
Two things I can think of might be causing the problem. There is an
option in the company setup under modules/production/job that allows
or disallows engineered jobs to be changed. Make sure it is
unchecked. However, if the job engineered checkbox is not checked
then I would think that should be a problem. I don't know of anything
else that controls that function.

--- In vantage@yahoogroups.com, "Allen R. Bernstein" <allenb@...> wrote:
>
> We are running into a slight problem here.
>
>
>
> We have searched for answers and now it's time to ask for some other
help.
>
>
>
> This is from one of the other techs I work with.
>
>
>
> Hi,
>
>
>
> I'm running into trouble using engineered parts in our live database.
> Everything works fine in the "training" database, but when I try to
use it
> in "live" or "test" (a recent backup of "live"), it just doesn't seem to
> work.
>
>
>
> When I create a job to make an engineered part, the Job Manager does not
> show any of the assembly details (operations, materials, etc). In
fact, the
> "Get Details" menu option is grayed out. This only happens when
using the
> live/test databases, training behaves perfectly.
>
>
>
> Thinking that it must just be something that's configured differently
> between the two databases, I created identical parts, operations,
resources,
> customers, etc but nothing seems to make a difference. I'm guessing that
> it's still some setting that's different between the two databases,
but I'm
> not sure where to look. Any ideas?
>
>
>
> Thanks in advance,
>
>
>
> Jeff
>
>
>
>
>
>
>
> Here are the steps I've followed in both "Test" and "Training" to create
> identical test parts, operations, resources, and customers.
>
>
>
>
>
> Run Part Maintenance
>
>
>
> === Create test-p1 part ===
>
>
>
> click "New" icon
>
> Enter part ID as "test-p1"
>
> Enter description and set type to "Purchased".
>
> All other options are left as default ("Use Part Rev", and "Quantity
> Bearing" are checked, all others unchecked)
>
> click "Save"
>
>
>
>
>
> === Create test-m1 part ===
>
>
>
> Click the "new" icon
>
> Enter Part ID as "test-m1"
>
> Enter description and set type to "Manufactured".
>
> Check "Non-Stock Item", all others are left as default ("Use Part
Rev", and
> "Quantity Bearing" are checked, all others unchecked)
>
>
>
> Click the arrow next to the "new" icon, choose "New Part Revision"
>
> Name the revision "A", enter description
>
>
>
> On the menu select Actions|Revision|Check Out Revision
>
>
>
> On the "Part Revision Checkout" screen
>
> Click "New ECO"
>
> "ECO Group Maintenance"
>
> enter "TEST" as Group ID, description, and ECO, click OK
>
> back on "Checkout", click OK
>
>
>
> from the menu, choose Actions|Revision|Engineering Workbench
>
>
>
> On the "Engineering Workbench"
>
> Actions|Operation|Add Operation
>
> Right click on the "Operation" dropdown, select Open
with|Operation Entry
>
>
>
> "Operation Maintenance"
>
> Create new operation "TEST", enter description, type
"Manufacturing",
> all other options unchecked or blank
>
> On the toolbar, click the dropdown next to the "new icon",
choose "New
> Resource Group Requirement"
>
> Right click on the "ResourceGrpID" cell, select Open
with|Resource Group
> Entry
>
>
>
> "Resource Group Maintenance"
>
> Click the new icon
>
> enter "TEST" as the group ID, enter a description.
>
> Right click on "Department", choose Open With|JC Department Entry
>
>
>
> "Job Department Maintenance"
>
> Enter "TEST" as the Job Dept ID, enter a description, leave "GL
> Division" and "GL Department" blank
>
> click save, close the "Job Department Maintenance" window
>
>
>
> Back on "Resource Group Maintenance", select "Test" as the
department,
> leave all other options as defaults
>
> Click the arrow next to the new icon, choose "New Resource"
>
> Enter "TEST" as the ResourceID, enter a description, leave all
other
> options as default
>
> Click save, close "Resource Group Maintenance"
>
>
>
> Back on "Operation Maintenance", enter "TEST" as the ResourceGroupID
>
> Click save, close "Operation Maintenance"
>
>
>
> Back on "Engineering Workbench", enter "TEST" as the operation
>
> From the menu, choose Actions|Material|Add Material
>
> Enter "test-p1" as the part ID
>
> Enter quantity as "1", leave all other options as default
>
> Click the revision tab, check "Approved"
>
> from the menu, choose Actions|Revision|Check In
>
> leave the default description of change, click "OK"
>
>
>
> Back on part maintenance, click save and close part maintenance
>
>
>
>
>
>
>
> === Create new Order ===
>
>
>
> Open Order Entry
>
>
>
> Click the "New" icon
>
> Right click on the "ID" field, choose Open With|Customer Entry
>
>
>
> "Customer Maintenance"
>
> Click the "New" icon
>
> Enter "TEST" as ID and description, change "Type" to "Customer"
>
> Click, the "Billing" tab, click the "Credit" subtab, uncheck
"Credit Hold"
>
> leave all else as default, click ok
>
> click save, close Customer Maintenance
>
>
>
> Click the dropdown next to the New icon, choose "New Line"
>
> under line detail, enter "test-m2" as the part, "Selling Quantity"
as 1,
> Need by Date to "2/22/2022" and check "Create Job"
>
> click Save
>
> click the "Create Jobs" button
>
> Click the "Releases tab"
>
> Right click on the Job Id, and choose Open With|Job Entry
>
>
>
> "Job Entry"
>
> from the menu, choose Actions|Job|Get Details <=================
THIS IS
> GREYED OUT, WHY?
>
>
>
>
>
>
>
>
>
>
>
>
>
> -Allen R. Bernstein
>
> Sales/Network Tech
>
> TCB Networks
>
> (269) 385-8180
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
5
Thanks you so much, this worked great!!



-Allen R. Bernstein

Sales/Network Tech

TCB Networks

(269) 385-8180



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
charles06072006
Sent: Friday, February 08, 2008 11:45 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Database issues....



Two things I can think of might be causing the problem. There is an
option in the company setup under modules/production/job that allows
or disallows engineered jobs to be changed. Make sure it is
unchecked. However, if the job engineered checkbox is not checked
then I would think that should be a problem. I don't know of anything
else that controls that function.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Allen
R. Bernstein" <allenb@...> wrote:
>
> We are running into a slight problem here.
>
>
>
> We have searched for answers and now it's time to ask for some other
help.
>
>
>
> This is from one of the other techs I work with.
>
>
>
> Hi,
>
>
>
> I'm running into trouble using engineered parts in our live database.
> Everything works fine in the "training" database, but when I try to
use it
> in "live" or "test" (a recent backup of "live"), it just doesn't seem to
> work.
>
>
>
> When I create a job to make an engineered part, the Job Manager does not
> show any of the assembly details (operations, materials, etc). In
fact, the
> "Get Details" menu option is grayed out. This only happens when
using the
> live/test databases, training behaves perfectly.
>
>
>
> Thinking that it must just be something that's configured differently
> between the two databases, I created identical parts, operations,
resources,
> customers, etc but nothing seems to make a difference. I'm guessing that
> it's still some setting that's different between the two databases,
but I'm
> not sure where to look. Any ideas?
>
>
>
> Thanks in advance,
>
>
>
> Jeff
>
>
>
>
>
>
>
> Here are the steps I've followed in both "Test" and "Training" to create
> identical test parts, operations, resources, and customers.
>
>
>
>
>
> Run Part Maintenance
>
>
>
> === Create test-p1 part ===
>
>
>
> click "New" icon
>
> Enter part ID as "test-p1"
>
> Enter description and set type to "Purchased".
>
> All other options are left as default ("Use Part Rev", and "Quantity
> Bearing" are checked, all others unchecked)
>
> click "Save"
>
>
>
>
>
> === Create test-m1 part ===
>
>
>
> Click the "new" icon
>
> Enter Part ID as "test-m1"
>
> Enter description and set type to "Manufactured".
>
> Check "Non-Stock Item", all others are left as default ("Use Part
Rev", and
> "Quantity Bearing" are checked, all others unchecked)
>
>
>
> Click the arrow next to the "new" icon, choose "New Part Revision"
>
> Name the revision "A", enter description
>
>
>
> On the menu select Actions|Revision|Check Out Revision
>
>
>
> On the "Part Revision Checkout" screen
>
> Click "New ECO"
>
> "ECO Group Maintenance"
>
> enter "TEST" as Group ID, description, and ECO, click OK
>
> back on "Checkout", click OK
>
>
>
> from the menu, choose Actions|Revision|Engineering Workbench
>
>
>
> On the "Engineering Workbench"
>
> Actions|Operation|Add Operation
>
> Right click on the "Operation" dropdown, select Open
with|Operation Entry
>
>
>
> "Operation Maintenance"
>
> Create new operation "TEST", enter description, type
"Manufacturing",
> all other options unchecked or blank
>
> On the toolbar, click the dropdown next to the "new icon",
choose "New
> Resource Group Requirement"
>
> Right click on the "ResourceGrpID" cell, select Open
with|Resource Group
> Entry
>
>
>
> "Resource Group Maintenance"
>
> Click the new icon
>
> enter "TEST" as the group ID, enter a description.
>
> Right click on "Department", choose Open With|JC Department Entry
>
>
>
> "Job Department Maintenance"
>
> Enter "TEST" as the Job Dept ID, enter a description, leave "GL
> Division" and "GL Department" blank
>
> click save, close the "Job Department Maintenance" window
>
>
>
> Back on "Resource Group Maintenance", select "Test" as the
department,
> leave all other options as defaults
>
> Click the arrow next to the new icon, choose "New Resource"
>
> Enter "TEST" as the ResourceID, enter a description, leave all
other
> options as default
>
> Click save, close "Resource Group Maintenance"
>
>
>
> Back on "Operation Maintenance", enter "TEST" as the ResourceGroupID
>
> Click save, close "Operation Maintenance"
>
>
>
> Back on "Engineering Workbench", enter "TEST" as the operation
>
> From the menu, choose Actions|Material|Add Material
>
> Enter "test-p1" as the part ID
>
> Enter quantity as "1", leave all other options as default
>
> Click the revision tab, check "Approved"
>
> from the menu, choose Actions|Revision|Check In
>
> leave the default description of change, click "OK"
>
>
>
> Back on part maintenance, click save and close part maintenance
>
>
>
>
>
>
>
> === Create new Order ===
>
>
>
> Open Order Entry
>
>
>
> Click the "New" icon
>
> Right click on the "ID" field, choose Open With|Customer Entry
>
>
>
> "Customer Maintenance"
>
> Click the "New" icon
>
> Enter "TEST" as ID and description, change "Type" to "Customer"
>
> Click, the "Billing" tab, click the "Credit" subtab, uncheck
"Credit Hold"
>
> leave all else as default, click ok
>
> click save, close Customer Maintenance
>
>
>
> Click the dropdown next to the New icon, choose "New Line"
>
> under line detail, enter "test-m2" as the part, "Selling Quantity"
as 1,
> Need by Date to "2/22/2022" and check "Create Job"
>
> click Save
>
> click the "Create Jobs" button
>
> Click the "Releases tab"
>
> Right click on the Job Id, and choose Open With|Job Entry
>
>
>
> "Job Entry"
>
> from the menu, choose Actions|Job|Get Details <=================
THIS IS
> GREYED OUT, WHY?
>
>
>
>
>
>
>
>
>
>
>
>
>
> -Allen R. Bernstein
>
> Sales/Network Tech
>
> TCB Networks
>
> (269) 385-8180
>
>
>
>
>
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]
6
The Job creation behavior you descirbe suggests Job Manager is not detecting any available approved Revs to Get Detials from (and thus is not even offering the Action).

Some things to try (to determine if it is a Job Manager specific problem or truly a problem with Part/PartPlant/PartRev data).

1. Do you get the same behavior when you try to create an equivalent Job using Job Entry?

2. If you artificially raise the TEST Part's Safety or Min to a ridiculously high level (exceeding on-hand + existing scheduled supply Job(s) qty) - and run a Full Regen MRP, do you get one or more UnFirmed Jobs for Part TEST? If so, do they have details?

3. If you change TEST Part to a NonStock Phantom and enter a sales Order Line Release against it - and then run Order Wizard, do you get a Make-Direct Job linked to the Order/Line/Release? If so, does it have job details?

Assuming none of these tests 'prove' it is an application (not data) bug - or reveal some missed data set up step, the db records now become suspect:

Unless I missed it in the email chain, you don't indicate the specific version you are running OR if you recently did any upgrades.

We discovered (yesterday) some subtle db tables changes were made between 403C & 403D. We had just done a pre-pilot legacy system to vantage db reimport and data maps the worked flawlessly for 403C resulted in problems in 403D.

I mention this as it is possible your ECO step of checking off the newly created Rev as Approved may no longer be sufficient. I suggest you go through the Actions menu and Approve the Rev.

There *may* be some new table field related to approval that a simple direct approval check off is not setting (a bug). Doing it through the Actions menu *may* result in success.

One final suggestion: Turn on Tracing in both Test and Training an reperform all steps side by side in both dbs (exactly - mouse click for mouse click and key stroke for key stroke).

When done, save each Trace Log and do a file comparison. Any differences in the Trace Logs *may* reveal the source(s) of the problem.

Good luck.

Rob Brown

"Allen R. Bernstein" <allenb@...> wrote:
We are running into a slight problem here.

We have searched for answers and now it's time to ask for some other help.

This is from one of the other techs I work with.

Hi,

I'm running into trouble using engineered parts in our live database.
Everything works fine in the "training" database, but when I try to use it
in "live" or "test" (a recent backup of "live"), it just doesn't seem to
work.

When I create a job to make an engineered part, the Job Manager does not
show any of the assembly details (operations, materials, etc). In fact, the
"Get Details" menu option is grayed out. This only happens when using the
live/test databases, training behaves perfectly.

Thinking that it must just be something that's configured differently
between the two databases, I created identical parts, operations, resources,
customers, etc but nothing seems to make a difference. I'm guessing that
it's still some setting that's different between the two databases, but I'm
not sure where to look. Any ideas?

Thanks in advance,

Jeff

Here are the steps I've followed in both "Test" and "Training" to create
identical test parts, operations, resources, and customers.

Run Part Maintenance

=== Create test-p1 part ===

click "New" icon

Enter part ID as "test-p1"

Enter description and set type to "Purchased".

All other options are left as default ("Use Part Rev", and "Quantity
Bearing" are checked, all others unchecked)

click "Save"

=== Create test-m1 part ===

Click the "new" icon

Enter Part ID as "test-m1"

Enter description and set type to "Manufactured".

Check "Non-Stock Item", all others are left as default ("Use Part Rev", and
"Quantity Bearing" are checked, all others unchecked)

Click the arrow next to the "new" icon, choose "New Part Revision"

Name the revision "A", enter description

On the menu select Actions|Revision|Check Out Revision

On the "Part Revision Checkout" screen

Click "New ECO"

"ECO Group Maintenance"

enter "TEST" as Group ID, description, and ECO, click OK

back on "Checkout", click OK

from the menu, choose Actions|Revision|Engineering Workbench

On the "Engineering Workbench"

Actions|Operation|Add Operation

Right click on the "Operation" dropdown, select Open with|Operation Entry

"Operation Maintenance"

Create new operation "TEST", enter description, type "Manufacturing",
all other options unchecked or blank

On the toolbar, click the dropdown next to the "new icon", choose "New
Resource Group Requirement"

Right click on the "ResourceGrpID" cell, select Open with|Resource Group
Entry

"Resource Group Maintenance"

Click the new icon

enter "TEST" as the group ID, enter a description.

Right click on "Department", choose Open With|JC Department Entry

"Job Department Maintenance"

Enter "TEST" as the Job Dept ID, enter a description, leave "GL
Division" and "GL Department" blank

click save, close the "Job Department Maintenance" window

Back on "Resource Group Maintenance", select "Test" as the department,
leave all other options as defaults

Click the arrow next to the new icon, choose "New Resource"

Enter "TEST" as the ResourceID, enter a description, leave all other
options as default

Click save, close "Resource Group Maintenance"

Back on "Operation Maintenance", enter "TEST" as the ResourceGroupID

Click save, close "Operation Maintenance"

Back on "Engineering Workbench", enter "TEST" as the operation

From the menu, choose Actions|Material|Add Material

Enter "test-p1" as the part ID

Enter quantity as "1", leave all other options as default

Click the revision tab, check "Approved"

from the menu, choose Actions|Revision|Check In

leave the default description of change, click "OK"

Back on part maintenance, click save and close part maintenance

=== Create new Order ===

Open Order Entry

Click the "New" icon

Right click on the "ID" field, choose Open With|Customer Entry

"Customer Maintenance"

Click the "New" icon

Enter "TEST" as ID and description, change "Type" to "Customer"

Click, the "Billing" tab, click the "Credit" subtab, uncheck "Credit Hold"

leave all else as default, click ok

click save, close Customer Maintenance

Click the dropdown next to the New icon, choose "New Line"

under line detail, enter "test-m2" as the part, "Selling Quantity" as 1,
Need by Date to "2/22/2022" and check "Create Job"

click Save

click the "Create Jobs" button

Click the "Releases tab"

Right click on the Job Id, and choose Open With|Job Entry

"Job Entry"

from the menu, choose Actions|Job|Get Details <================= THIS IS
GREYED OUT, WHY?

-Allen R. Bernstein

Sales/Network Tech

TCB Networks

(269) 385-8180

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






---------------------------------
Never miss a thing. Make Yahoo your homepage.

[Non-text portions of this message have been removed]
7
Mr. Charles: I ran into the same error using my Vista 64bit and found
the following on the Progress site. Add the registry key
Workarounds2=40696 to fix this.

ID: P116845
Title: "Reserved error -7748 when attempting to link a OpenEdge 10.1x
Database table in Microsoft Access"

Created: 06/20/2006 Last Modified: 09/24/2007
Status: Unverified

Facts:

OpenEdge 10.1A
OpenEdge 10.1B
Progress OpenEdge 10.1A driver
Progress OpenEdge 10.1B driver
Windows



Symptoms:

Error attempting to link a OpenEdge Database table in MS Access
Reserved error (-7748): there is no message for this error
Error in ODBC trace file
DIAG [01004] [DataDirect][ODBC Progress OpenEdge Wire Protocol driver]
String data, right truncated. Error in column 10. (0)
Problem occurs when using the 5.1 DataDirect driver shipped with 10.1A
Problem occurs when using the 5.1 DataDirect driver shipped with 10.1B
Problem does not occur with the 4.2 DataDirect driver shipped with 10.0B




Cause:
Known issue with the DataDirect driver


Fixes:

WARNING - You should always make a backup of the Registry before any
changes.

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 (The string value that must be added
to Windows XP SP2 and Progress 10.1A02 is WorkArounds2=40960)

7. Click OK

8. Close RegEdit

PCs running Windows 95 and 98 need to be rebooted for this setting to
take effect

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. Thus,
the driver returns a warning, "01004 Data truncated", and returns a
null character to Microsoft Access. Microsoft Access then passes
error -7748. Setting this workaround causes Microsoft Access to not
pass the error -7748.


Good Luck,

Dave Olender dolender@...
Ph: 651-246-3281


--- In vantage@yahoogroups.com, "charles06072006" <shadow031449@...>
wrote:
>
> I have been trying to add a link table to an access database with the
> new Progress OpenEdge 10.1B ODBC driver for 8.03.403d. Every time I
> make the attempt I get this error message:
>
> Reserved error (-7748); there is no message for this error.
>
> I have existing link tables in the access database and they work fine.
> I just can't set up a new link. If I delete a current linked table I
> am also not able to relink it. I have tried this in Windows Vista
> (32bit) with Office 2007 and in Windows XP (32bit) with Office 2003.
> Same message both places.
>
> Anyone have any ideas?
>