Do most Packaged ERP systems lock down the Data (No write access)

[GBalcom]

I've had experience with 3 out of the box software programs that used an SQL back end. 2 of the 3 allowed an open read/write connection.

Our current ERP system at work only allows a read access connection via ODBC. Frankly, it doesn't meet all of our needs moving into the future, and I would much prefer to be able to write specific apps in access as needed, and push data back to the system as needed.

I've spoke with the company, and they simply don't allow write access. Is this common? I kind of feel like our data is being held hostage....I love the base program, (don't really want to reinvent the wheel), but we will benefit greatly from specific functions unique to our business that is not provided with this program.

 

[pbaldy]

I can't address how common it is, but I understand why they might do it. If you are allowed to write to the data, they can no longer be held accountable for it. You could break referential integrity, circumvent audit trails, etc. It's a "too many chefs in the kitchen" situation. Something breaks and you expect them to stand behind it even though you may have caused the problem.

I would argue you data isn't held hostage, as you have full access to it. You just can't change it outside their processes. Perhaps an option is creating tables in a database you control and link to theirs. They have tblCustomers and you add tblCustomersExtraStuff and join on their primary key. That's completely untested though.

 

[GBalcom]

Pbaldy,
That is an excellent point you bring up about linked tables. I can see that working in certain cases, where fields are lacking. The instance for me that started this thread is the inability to import estimate or project level information into the program. We are working on a web interface (think catalog based store front). When an order is placed through the website, I need it to seamlessly integrate with our internal systems (I will have read access to the websites back end to be able to pull the information needed).
I'm in touch with the developer, and I'm hoping he will allow us specific update/insert authority with his direction. We'll see.

 

[pbaldy]

I would certainly expect the developer to provide some sort of import functionality. Important not only for your situation, but for new users of the program to import existing data. Your situation is trickier because you likely want to be able to automate it, so ideally you would need write access to the data.

 

[scott-atkinson]

My company bought an out of the box ERP system many years ago, that was a Read Access only, we modified the system to such an extent that the developer will no longer support it.

 

[GBalcom]

Scott,
did you eventually can write access to it? If not, did you add your own linked "sister" tables?

 

[scott-atkinson]

Scott,
did you eventually can write access to it? If not, did you add your own linked "sister" tables?

We have Read Write access to the main ERP database, but it came at a heavily modified cost to the base product, and as said the developer has refused to support the base product now.

We have other products purchased from the developer than link to the ERP, they should have linked seamlessly but because we modded the ERP we have had to build interfaces between the new bought systems and the original ERP.

The Developer supports the new systems as they have not been modded.