MS Access Linked Table to PartOpr

I am trying to pull a report that includes the mfgcomments field from
the part table. When I query that field from a BAQ, I get atleast a
portion of the results (Scrolls of screen). If I query it from Excel,
or Crystal, I get nothing from that field. If I use SQL explorer, I
get about 254 characters of the field.

I am not getting any error messages, which is what really confuses
me. I am familiar with the field length errors from trying to query
the change logs, but in this case, I am not getting any errors.

Also, I was unable to find the answerbook listed below. Has it been
removed?
Thanks,
Craig


--- In vantage@yahoogroups.com, "A Mercer Sisson" <onelist@...> wrote:
>
> Thanks, you are quote right. Once I realized that I adjusted the
SQL
> widths in the wrong database and corrected the proper one all worked
> as described in the answerbook article. Since we are not in
> production with 8.x yet I have several databases in different
> locations. My apologies for the confusion.
>
> Thanks for your help.
>
> Mercer Sisson
>
> --- In vantage@yahoogroups.com, "Ross Hughes" <ross.hughes@> wrote:
> >
> > Yes, it is the SQL width function that needs adjusting.
> >
> > It works fine when I adjusted it. It is all spelled out in the
> answer book
> > page.
> >
> > Ross
> >
> > -----Original Message-----
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
> Behalf Of
> > A Mercer Sisson
> > Sent: Thursday, August 21, 2008 1:41 PM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Re: MS Access Linked Table to PartOpr
> >
> > You think the field width is too LOW?
> >
> > All of the memo type fields have a width of 2000, which always
seems
> > to translate to a Memo field in Access. It is possible that I
have
> > more than 1000 characters in come of the comment fields, could
that be
> > the culprit?
> >
> > I have adjusted the field widths using the dbtools tool as well
as the
> > data dictionary to no avail, but I did not increase any of the
widths.
> >
> > I am guessing that this error message is a bit of a red herring
and
> > that the ODBC driver is passing an error code that the Jet Engine
does
> > not understand.
> >
> > --- In vantage@yahoogroups.com, "Ross Hughes" <ross.hughes@>
wrote:
> > >
> > > I have found two ways around this. One it to create a view with
> > only the
> > > fields you want (hopefully the field you want is not the
culprit).
> > >
> > >
> > >
> > > The second is to read answerbook page 7069MPS.
> > >
> > >
> > >
> > > It basically says that the error comes from the SQL width
setting
> in the
> > > Data Dictionary being set too low for long fields like Part
> Description,
> > > etc.
> > >
> > >
> > >
> > > You need to go to the server and start the data dictionary in
write
> > mode and
> > > adjust the width settings for the required fields. It is
spelled
> > out in the
> > > AB page.
> > >
> > >
> > >
> > > It seems to work well.
> > >
> > >
> > >
> > > Ross
> > >
> > >
> > >
> > > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On
> > Behalf Of
> > > Gary Parfrey
> > > Sent: Friday, August 15, 2008 8:45 AM
> > > To: vantage@yahoogroups.com
> > > Subject: RE: [Vantage] Re: MS Access Linked Table to PartOpr
> > >
> > >
> > >
> > > John
> > >
> > > Did you include all the fields in the view you created?
> > >
> > > Just try including a few fields? You may be able to find the
field in
> > > issue, probably a comments field?
> > >
> > > Gary
> > >
> > > Dot Net IT Limited, Reg No 4412519
> > >
> > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > > [mailto:vantage@yahoogroups.com <mailto:vantage%
40yahoogroups.com>
> ] On
> > > Behalf
> > > Of John Atwood
> > > Sent: 15 August 2008 02:01
> > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > > Subject: [Vantage] Re: MS Access Linked Table to PartOpr
> > >
> > > I have the same problem with the PartOpr table and have not
found a
> > > direct solution. I'm using a workaround by writing a BAQ from
the
> table
> > > with the fields I need. I then setup the BAQ export on a
recurring
> task
> > > and link MS Access to the .CSV file created from the BAQ.
> > >
> > > John Atwood
> > > Stellar Microelectronics
> > >
> > > --- In vantage@yahoogroups.com <mailto:vantage%
40yahoogroups.com>
> > > <mailto:vantage%40yahoogroups.com> ,
> > > "amsisson" <onelist@> wrote:
> > > >
> > > > When I try to create a linked table in MS Access to the
PartOpr
> table
> > > > in Vantage 8.x I get a "field size is to large" but it does
not tell
> > > > me which field is too large. I have created a View with out
effect.
> > > > I can create a Passthru query, but that won't allow what I
need
> to do.
> > > >
> > > > Any suggestions?
> > > >
> > > > Mercer Sisson
> > > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
> > ------------------------------------
> >
> > Useful links for the Yahoo!Groups Vantage Board are: ( Note: You
> must have
> > already linked your email address to a yahoo id to enable
access. )
> > (1) To access the Files Section of our Yahoo!Group for Report
> Builder and
> > Crystal Reports and other 'goodies', please goto:
> > http://groups.yahoo.com/group/vantage/files/.
> > (2) To search through old msg's goto:
> > http://groups.yahoo.com/group/vantage/messages
> > (3) To view links to Vendors that provide Vantage services goto:
> > http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
> >
>
When I try to create a linked table in MS Access to the PartOpr table
in Vantage 8.x I get a "field size is to large" but it does not tell
me which field is too large. I have created a View with out effect.
I can create a Passthru query, but that won't allow what I need to do.

Any suggestions?

Mercer Sisson
I have the same problem with the PartOpr table and have not found a
direct solution. I'm using a workaround by writing a BAQ from the table
with the fields I need. I then setup the BAQ export on a recurring task
and link MS Access to the .CSV file created from the BAQ.

John Atwood
Stellar Microelectronics

--- In vantage@yahoogroups.com, "amsisson" <onelist@...> wrote:
>
> When I try to create a linked table in MS Access to the PartOpr table
> in Vantage 8.x I get a "field size is to large" but it does not tell
> me which field is too large. I have created a View with out effect.
> I can create a Passthru query, but that won't allow what I need to do.
>
> Any suggestions?
>
> Mercer Sisson
>
John



Did you include all the fields in the view you created?



Just try including a few fields? You may be able to find the field in
issue, probably a comments field?



Gary



Dot Net IT Limited, Reg No 4412519

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of John Atwood
Sent: 15 August 2008 02:01
To: vantage@yahoogroups.com
Subject: [Vantage] Re: MS Access Linked Table to PartOpr



I have the same problem with the PartOpr table and have not found a
direct solution. I'm using a workaround by writing a BAQ from the table
with the fields I need. I then setup the BAQ export on a recurring task
and link MS Access to the .CSV file created from the BAQ.

John Atwood
Stellar Microelectronics

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"amsisson" <onelist@...> wrote:
>
> When I try to create a linked table in MS Access to the PartOpr table
> in Vantage 8.x I get a "field size is to large" but it does not tell
> me which field is too large. I have created a View with out effect.
> I can create a Passthru query, but that won't allow what I need to do.
>
> Any suggestions?
>
> Mercer Sisson
>





[Non-text portions of this message have been removed]
I have found two ways around this. One it to create a view with only the
fields you want (hopefully the field you want is not the culprit).



The second is to read answerbook page 7069MPS.



It basically says that the error comes from the SQL width setting in the
Data Dictionary being set too low for long fields like Part Description,
etc.



You need to go to the server and start the data dictionary in write mode and
adjust the width settings for the required fields. It is spelled out in the
AB page.



It seems to work well.



Ross



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Gary Parfrey
Sent: Friday, August 15, 2008 8:45 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: MS Access Linked Table to PartOpr



John

Did you include all the fields in the view you created?

Just try including a few fields? You may be able to find the field in
issue, probably a comments field?

Gary

Dot Net IT Limited, Reg No 4412519

From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf
Of John Atwood
Sent: 15 August 2008 02:01
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: [Vantage] Re: MS Access Linked Table to PartOpr

I have the same problem with the PartOpr table and have not found a
direct solution. I'm using a workaround by writing a BAQ from the table
with the fields I need. I then setup the BAQ export on a recurring task
and link MS Access to the .CSV file created from the BAQ.

John Atwood
Stellar Microelectronics

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> ,
"amsisson" <onelist@...> wrote:
>
> When I try to create a linked table in MS Access to the PartOpr table
> in Vantage 8.x I get a "field size is to large" but it does not tell
> me which field is too large. I have created a View with out effect.
> I can create a Passthru query, but that won't allow what I need to do.
>
> Any suggestions?
>
> Mercer Sisson
>

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





[Non-text portions of this message have been removed]
Hi Gary,
I was using it for a custom WIP status report and only included the
fields I needed for the report. I've had no luck determining which
field is causing the table to not be able to be linked. I would
suspect the "CommentText". However, while I also get the same error
on the ECOOpr table, I've not had problems with JobOper which should
have the same essential structure and data. Incidently, if you need
the Comment Text field, it does not work well with .CSV files if you
have hard returns in your data.

--- In vantage@yahoogroups.com, "Gary Parfrey" <garyp@...> wrote:
>
> John
>
>
>
> Did you include all the fields in the view you created?
>
>
>
> Just try including a few fields? You may be able to find the field
in
> issue, probably a comments field?
>
>
>
> Gary
>
>
>
> Dot Net IT Limited, Reg No 4412519
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> Of John Atwood
> Sent: 15 August 2008 02:01
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: MS Access Linked Table to PartOpr
>
>
>
> I have the same problem with the PartOpr table and have not found a
> direct solution. I'm using a workaround by writing a BAQ from the
table
> with the fields I need. I then setup the BAQ export on a recurring
task
> and link MS Access to the .CSV file created from the BAQ.
>
> John Atwood
> Stellar Microelectronics
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "amsisson" <onelist@> wrote:
> >
> > When I try to create a linked table in MS Access to the PartOpr
table
> > in Vantage 8.x I get a "field size is to large" but it does not
tell
> > me which field is too large. I have created a View with out
effect.
> > I can create a Passthru query, but that won't allow what I need
to do.
> >
> > Any suggestions?
> >
> > Mercer Sisson
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
I have a view set up for that table and have no problems. Here is my
structure:




Hope this helps (not sure what fields you need in your view)


Kersten MacLennan
IT/ERP Analyst
Semrock, Inc.
3625 Buffalo Rd.,
Suite 6
Rochester, NY 14624
585-594-7009
585-594-7095 fax

kmaclennan@...

The Standard in Optical Filters for Biotech & Analytical Instrumentation


Hundreds of Thousands of Ion Beam Sputtered filters delivered -
extensive inventory now!

The information contained in this message and any attachments may be
privileged, confidential, and protected from disclosure. If the reader
of this message is not the intended recipient, or any agent responsible
for delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, or copying of this
communication may be unlawful and therefore strictly prohibited. If you
received this message in error, please reply to the message and delete
it. Thank you




________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of John Atwood
Sent: Thursday, August 14, 2008 9:01 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: MS Access Linked Table to PartOpr



I have the same problem with the PartOpr table and have not found a
direct solution. I'm using a workaround by writing a BAQ from the table
with the fields I need. I then setup the BAQ export on a recurring task
and link MS Access to the .CSV file created from the BAQ.

John Atwood
Stellar Microelectronics

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"amsisson" <onelist@...> wrote:
>
> When I try to create a linked table in MS Access to the PartOpr table
> in Vantage 8.x I get a "field size is to large" but it does not tell
> me which field is too large. I have created a View with out effect.
> I can create a Passthru query, but that won't allow what I need to do.
>
> Any suggestions?
>
> Mercer Sisson
>






[Non-text portions of this message have been removed]
It looks as though part of your post is missing. Can you please
provide details of your view definition.


--- In vantage@yahoogroups.com, "Kersten MacLennan" <kmaclennan@...>
wrote:
>
> I have a view set up for that table and have no problems. Here is my
> structure:
>
>
>
>
> Hope this helps (not sure what fields you need in your view)
>
>
> Kersten MacLennan
> IT/ERP Analyst
> Semrock, Inc.
> 3625 Buffalo Rd.,
> Suite 6
> Rochester, NY 14624
> 585-594-7009
> 585-594-7095 fax
>
> kmaclennan@...
>
> The Standard in Optical Filters for Biotech & Analytical Instrumentation
>
>
> Hundreds of Thousands of Ion Beam Sputtered filters delivered -
> extensive inventory now!
>
> The information contained in this message and any attachments may be
> privileged, confidential, and protected from disclosure. If the reader
> of this message is not the intended recipient, or any agent responsible
> for delivering this message to the intended recipient, you are hereby
> notified that any dissemination, distribution, or copying of this
> communication may be unlawful and therefore strictly prohibited. If you
> received this message in error, please reply to the message and delete
> it. Thank you
>
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of John Atwood
> Sent: Thursday, August 14, 2008 9:01 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: MS Access Linked Table to PartOpr
>
>
>
> I have the same problem with the PartOpr table and have not found a
> direct solution. I'm using a workaround by writing a BAQ from the table
> with the fields I need. I then setup the BAQ export on a recurring task
> and link MS Access to the .CSV file created from the BAQ.
>
> John Atwood
> Stellar Microelectronics
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "amsisson" <onelist@> wrote:
> >
> > When I try to create a linked table in MS Access to the PartOpr table
> > in Vantage 8.x I get a "field size is to large" but it does not tell
> > me which field is too large. I have created a View with out effect.
> > I can create a Passthru query, but that won't allow what I need to do.
> >
> > Any suggestions?
> >
> > Mercer Sisson
> >
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
You think the field width is too LOW?

All of the memo type fields have a width of 2000, which always seems
to translate to a Memo field in Access. It is possible that I have
more than 1000 characters in come of the comment fields, could that be
the culprit?

I have adjusted the field widths using the dbtools tool as well as the
data dictionary to no avail, but I did not increase any of the widths.

I am guessing that this error message is a bit of a red herring and
that the ODBC driver is passing an error code that the Jet Engine does
not understand.

--- In vantage@yahoogroups.com, "Ross Hughes" <ross.hughes@...> wrote:
>
> I have found two ways around this. One it to create a view with
only the
> fields you want (hopefully the field you want is not the culprit).
>
>
>
> The second is to read answerbook page 7069MPS.
>
>
>
> It basically says that the error comes from the SQL width setting in the
> Data Dictionary being set too low for long fields like Part Description,
> etc.
>
>
>
> You need to go to the server and start the data dictionary in write
mode and
> adjust the width settings for the required fields. It is spelled
out in the
> AB page.
>
>
>
> It seems to work well.
>
>
>
> Ross
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of
> Gary Parfrey
> Sent: Friday, August 15, 2008 8:45 AM
> To: vantage@yahoogroups.com
> Subject: RE: [Vantage] Re: MS Access Linked Table to PartOpr
>
>
>
> John
>
> Did you include all the fields in the view you created?
>
> Just try including a few fields? You may be able to find the field in
> issue, probably a comments field?
>
> Gary
>
> Dot Net IT Limited, Reg No 4412519
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf
> Of John Atwood
> Sent: 15 August 2008 02:01
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: MS Access Linked Table to PartOpr
>
> I have the same problem with the PartOpr table and have not found a
> direct solution. I'm using a workaround by writing a BAQ from the table
> with the fields I need. I then setup the BAQ export on a recurring task
> and link MS Access to the .CSV file created from the BAQ.
>
> John Atwood
> Stellar Microelectronics
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> ,
> "amsisson" <onelist@> wrote:
> >
> > When I try to create a linked table in MS Access to the PartOpr table
> > in Vantage 8.x I get a "field size is to large" but it does not tell
> > me which field is too large. I have created a View with out effect.
> > I can create a Passthru query, but that won't allow what I need to do.
> >
> > Any suggestions?
> >
> > Mercer Sisson
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
Yes, it is the SQL width function that needs adjusting.

It works fine when I adjusted it. It is all spelled out in the answer book
page.

Ross

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
A Mercer Sisson
Sent: Thursday, August 21, 2008 1:41 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: MS Access Linked Table to PartOpr

You think the field width is too LOW?

All of the memo type fields have a width of 2000, which always seems
to translate to a Memo field in Access. It is possible that I have
more than 1000 characters in come of the comment fields, could that be
the culprit?

I have adjusted the field widths using the dbtools tool as well as the
data dictionary to no avail, but I did not increase any of the widths.

I am guessing that this error message is a bit of a red herring and
that the ODBC driver is passing an error code that the Jet Engine does
not understand.

--- In vantage@yahoogroups.com, "Ross Hughes" <ross.hughes@...> wrote:
>
> I have found two ways around this. One it to create a view with
only the
> fields you want (hopefully the field you want is not the culprit).
>
>
>
> The second is to read answerbook page 7069MPS.
>
>
>
> It basically says that the error comes from the SQL width setting in the
> Data Dictionary being set too low for long fields like Part Description,
> etc.
>
>
>
> You need to go to the server and start the data dictionary in write
mode and
> adjust the width settings for the required fields. It is spelled
out in the
> AB page.
>
>
>
> It seems to work well.
>
>
>
> Ross
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of
> Gary Parfrey
> Sent: Friday, August 15, 2008 8:45 AM
> To: vantage@yahoogroups.com
> Subject: RE: [Vantage] Re: MS Access Linked Table to PartOpr
>
>
>
> John
>
> Did you include all the fields in the view you created?
>
> Just try including a few fields? You may be able to find the field in
> issue, probably a comments field?
>
> Gary
>
> Dot Net IT Limited, Reg No 4412519
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf
> Of John Atwood
> Sent: 15 August 2008 02:01
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: MS Access Linked Table to PartOpr
>
> I have the same problem with the PartOpr table and have not found a
> direct solution. I'm using a workaround by writing a BAQ from the table
> with the fields I need. I then setup the BAQ export on a recurring task
> and link MS Access to the .CSV file created from the BAQ.
>
> John Atwood
> Stellar Microelectronics
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> ,
> "amsisson" <onelist@> wrote:
> >
> > When I try to create a linked table in MS Access to the PartOpr table
> > in Vantage 8.x I get a "field size is to large" but it does not tell
> > me which field is too large. I have created a View with out effect.
> > I can create a Passthru query, but that won't allow what I need to do.
> >
> > Any suggestions?
> >
> > Mercer Sisson
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>



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

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
Thanks, you are quote right. Once I realized that I adjusted the SQL
widths in the wrong database and corrected the proper one all worked
as described in the answerbook article. Since we are not in
production with 8.x yet I have several databases in different
locations. My apologies for the confusion.

Thanks for your help.

Mercer Sisson

--- In vantage@yahoogroups.com, "Ross Hughes" <ross.hughes@...> wrote:
>
> Yes, it is the SQL width function that needs adjusting.
>
> It works fine when I adjusted it. It is all spelled out in the
answer book
> page.
>
> Ross
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of
> A Mercer Sisson
> Sent: Thursday, August 21, 2008 1:41 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: MS Access Linked Table to PartOpr
>
> You think the field width is too LOW?
>
> All of the memo type fields have a width of 2000, which always seems
> to translate to a Memo field in Access. It is possible that I have
> more than 1000 characters in come of the comment fields, could that be
> the culprit?
>
> I have adjusted the field widths using the dbtools tool as well as the
> data dictionary to no avail, but I did not increase any of the widths.
>
> I am guessing that this error message is a bit of a red herring and
> that the ODBC driver is passing an error code that the Jet Engine does
> not understand.
>
> --- In vantage@yahoogroups.com, "Ross Hughes" <ross.hughes@> wrote:
> >
> > I have found two ways around this. One it to create a view with
> only the
> > fields you want (hopefully the field you want is not the culprit).
> >
> >
> >
> > The second is to read answerbook page 7069MPS.
> >
> >
> >
> > It basically says that the error comes from the SQL width setting
in the
> > Data Dictionary being set too low for long fields like Part
Description,
> > etc.
> >
> >
> >
> > You need to go to the server and start the data dictionary in write
> mode and
> > adjust the width settings for the required fields. It is spelled
> out in the
> > AB page.
> >
> >
> >
> > It seems to work well.
> >
> >
> >
> > Ross
> >
> >
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
> Behalf Of
> > Gary Parfrey
> > Sent: Friday, August 15, 2008 8:45 AM
> > To: vantage@yahoogroups.com
> > Subject: RE: [Vantage] Re: MS Access Linked Table to PartOpr
> >
> >
> >
> > John
> >
> > Did you include all the fields in the view you created?
> >
> > Just try including a few fields? You may be able to find the field in
> > issue, probably a comments field?
> >
> > Gary
> >
> > Dot Net IT Limited, Reg No 4412519
> >
> > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
] On
> > Behalf
> > Of John Atwood
> > Sent: 15 August 2008 02:01
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Re: MS Access Linked Table to PartOpr
> >
> > I have the same problem with the PartOpr table and have not found a
> > direct solution. I'm using a workaround by writing a BAQ from the
table
> > with the fields I need. I then setup the BAQ export on a recurring
task
> > and link MS Access to the .CSV file created from the BAQ.
> >
> > John Atwood
> > Stellar Microelectronics
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > <mailto:vantage%40yahoogroups.com> ,
> > "amsisson" <onelist@> wrote:
> > >
> > > When I try to create a linked table in MS Access to the PartOpr
table
> > > in Vantage 8.x I get a "field size is to large" but it does not tell
> > > me which field is too large. I have created a View with out effect.
> > > I can create a Passthru query, but that won't allow what I need
to do.
> > >
> > > Any suggestions?
> > >
> > > Mercer Sisson
> > >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You
must have
> already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report
Builder and
> Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>