Aspel SAE synchronization module for the osCommerce Product Manager for Windows (oscpmwin) 0.2.1.7.


This is a program that connects to your SAE inventory application (from ASPEL) database and then answer the queries of the osCommerce Product Manager so it can synchronize quantitites or prices in your osCommerce store. This assumes your authoritative data is stored in the Aspel SAE database and not in the osCommerce store.

IMPORTANT NOTE: We DON'T endorse or recommend the SAE product or any products from the ASPEL company in any way.

Requirements.

  • The osCommerce Product Manager for Windows installed and working.
  • An Aspel SAE inventory program installed and working, with a Paradox database back-end. (The module can work with other database types supported by Aspel SAE [except the obsolete native type]).

Installation.

1) Get the files.
Get the files from http://www.mariovaldez.net/software/oscpm_aspel/

2) Unpack.
Open and extract the files from the zip package using a Zip decompressor to the modules directory of your osCommerce Product Manager directory. We recommend 7-ZIP (free, open-source), but you can use WinZip, WinRAR or any other ZIP software.

3) Configure.
Run the OSCPMWin application and open the Configuration window, go to the External modules tab and there you will find three default modules listed as Actualizar Existencias por Clave, and Actualizar Precios por Clave. Edit each module configuration to match your Aspel SAE setup. In the module parameter field you will find a line like this:

"c:\saewin\" inve01 clv_art exist 27572 p

The first item must match the directory path to the database files of your Aspel SAE setup. The second item is the name of the inventory database table, usually named inveXX; this should match your setup.

4) Test.
Connect to your osCommerce store using the OSCPMWin application, select some products, go to the Tools menu and choose any of the External Modules listed. The synchronization module window will appear, showing the queries from the OSCPMWin application. When finished, the module should close and a confirmation listing will appear, showing the old and new values found.

5) You are done.

Download.

  • The current version (0.2.1.7, 2006/02/08) is available as a zip file (380k).
  • There is a Readme file included with all packages.
  • There is a Changelog file included with all packages.
  • There is a signed checksum file that lets you verify the integrity of the downloaded file.
  • There is a License file included with all packages.

License.

OSCPM-ASPEL2 module for the osCommerce Product Manager for Windows (oscpm1_aspel2). Copyright 2004-2006 by Mario A. Valdez-Ramirez.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

OSI-Certified logo

Questions, comments, suggestions.

You can send your questions, comments or suggestions by email.

Don't hesitate to contact the author by email (mario@mariovaldez.org).


Download the source code (ASPEL module).

You can use the source code of this sample module to create your own synchronization external modules.

  • The source code of the sample ASPEL synchronization module (0.2.1.7, 2006/02/08) is available as a tar.bz2 package (461k).
  • There is a signed checksum file that lets you verify the integrity of the downloaded file.
  • There is a License file for the source code (which is a BSD-like license).

This source-code package includes the debugging map file and the reference executable file.

Important note:

If you modify the source code and redistribute any module, please check the licensing terms of the ASPEL module and the components used. The ASPEL module source code is compatible with most open-source licenses (you can release your module under a BSD-like, MIT-like, MPL, GPL or LGPL license). The INDY components (required) are compatible with most open-source licenses.

If you develop your modules without using any of this source code, none of this apply to you and you can use whatever license you like. The synchronization modules do not link directly to the OSCPMWin application, they work like client-server software and so they can have different licensing terms.

Browse the source files (0.2.1.7).

Build the source code (ASPEL module).

You need Borland Delphi to compile it (we have used Delphi 6 and currently use Turbo Delphi Win32).
You will also need the following components to compile:

Older versions (ASPEL module).

If you are looking for some other file (including older versions), you can browse the /files/source/ directory. But be aware that some source packages are from unreleased versions that may or may not work.

Some older versions of the module required the following components to compile:


Unsolved bugs and not implemented features

For a list of known bugs to be fixed and features to be implemented in the OSCPMWin ASPEL module, check the BugTracker.

 
 
NA fum/lmd: 2011.05.06
Copyright ©1994-2017 by Mario A. Valdez-Ramírez.
no siga este enlace / do not follow this link