Re: System-Link

I think System-links primary advantage is the ability to provide a single point of control for business logic. In other words, System-link uses the client architecture and therefore uses all of the defaults and edits defined in Integrator. When .NET touches the files directly, it has none of the business logic except the restraints put in at the DB level (primary key, unique, etc).

Even if the primary function of your applications is to report, and not maintain data, there are significant advantages to using systemlink. It is easy to develop a "query" in Power link and export that to System link. In that way you can ensure that various different uses of the data operate on the same data sets.

To date, I've always copied and modified the System link request that you get from the menu option. I thought I remembered seeing the ability to use named views and subsets, is that available, or did I just make that up and start believing in it?

Josh




-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx] On Behalf Of ibm
Sent: Friday, May 01, 2009 7:07 AM
To: 'mapics-l@xxxxxxxxxxxx'
Subject: [MAPICS-L] System-Link

Currently we have many apps developed with .NET and VB6 and Access/SQL databases that interface with the Mapics DB.



What advantages/disadvantages would System-Link provide us?



_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/mapics-l.