x Want to participate? Join the group to interact
Options
  • Replies 3 replies
  • Subscribers 106 subscribers
  • Views 678 views
  • Users 0 members are here
Browse Forums
Announcements
292
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
43
topics
90
replies
Payroll, Time Tracking, and Job Cost
775
topics
1k
replies
Reporting and Analytics
960
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Rick Barone

Why won't a Sage 100 Mas90 32 bit ODBC driver allow wrire access when exporting FedEx tracking numbers to a SO-HEADER field contaiing a maximum 35 character limit? Version 4.0

Posted By

Please advise if this is a "Write" permissions issue that needs to be set within Sage.  Only reason I can advance for the processed shipment data to not be able to post to the referenced table and table field.

  • The ODBC driver that ships with MAS90 / Sage 100 is read only.

    Use an import job (Visual Integrator) if you have that module.

    Note: Read-Only ODBC is purposeful to protect the data integrity, since ODBC bypasses all the programmed system logic.

  • About 15 years ago I worked with a FedEx tech and we used Send Keys to write back that information.  You had to have the Sage 100 panel open and the pointer in the correct field and then active the Send Keys code in FedEx and it worked. Took a lot of work.  It is the same basic principle that UPS used with Crossware. 

  • FormerMember
    FormerMember in reply to Kevin M

    ODBC is useless with Payroll and credit card based tables due to encryption.

*Community Hub is the new name for Sage City