none
Complex POS system with data online. RRS feed

  • Question

  • I have spent a few years building a complex Point of sale system in MS Access,  it uses Cash Drawers, Printers, Label Printers and so on.   What I would like to do is have the data portion of this online.   That way I can have multiple stores access the same data at different locations.   The important part is I need it to connect from a desktop Access front end.  Basically front end is MS access local, connecting to back end Data online.

    Is there any way to do this that is not rebuilding this from the ground up?

    Thanks

    Tuesday, June 14, 2016 4:05 PM

All replies

  • See: http://www.devhut.net/tag/ms-access-hybrid-databases/

    Another option would be to use RDP, CITRIX, ... to remotely connect to a standard db on a computer/server.  This has much better performance and doesn't require office365 accounts, ...

    That all said, IMHO, Access is simply not the tool for the job.  When you get into wanting to share data over a WAN (the www) then Access simply does not cut the mustard no matter how hard you try.  You are better investing in a Real Web Database (PHP, .NET, ...).

    Good luck, I suspect you have fun times ahead of you!


    Daniel Pineault, 2010-2012 Microsoft MVP
    http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Tuesday, June 14, 2016 4:43 PM
  • One more wet blanket for you..Today's industry standard for POS is touch screen at the register/order stations.

    Bill Mosca
    www.thatlldoit.com
    http://tech.groups.yahoo.com/group/MS_Access_Professionals

    Tuesday, June 14, 2016 5:16 PM
  • I will second DP's advice.  Beginning with Office 2013 the product is '365 Aware' and one can link the standard front end to SharePoint lists in the cloud 365 account.  I have done it a few times.  It is suitable for some geographically separated internal applications.  But it must be a new build in my experience with definite reliance on all table relationships being between autonumber key fields.  It cannot be public facing and if there are any issues about users looking directly at table data (they can if they are so inclined) then it is not suitable. 

    So for a mature & complex app - probably built before Access 2013 - and with a time critical aspect such as POS (assuming the customer is standing there or on the phone waiting) it is much more straight forward to manage a remote desktop/application deployment instead.  It would be far easier to trouble shoot and maintain.

    Whether or not Access is even the correct development environment for a POS - or any touch screen style app - is kind of a different topic.  I also tend to agree with BM that it is not. 

    Wednesday, June 15, 2016 1:19 PM