If you are software developer or database administrator – we would like to give you the clues on Crystal Report creation for Microsoft RMS
- Database: Microsoft SQL Server or MSDE – this means that you can deploy native SQL driver for connection or use ODBC for flexibility.
- Tables Structure – it is extremely self-explanatory: Customer, Transaction (invoices, returns, layaways and others), TransactionAmount, Cashier, Tender to give you examples
- Links – Usually master table has ID column and Transaction-related table links by [Entity]ID column: Transaction.CustomerID=Customer.ID to give the idea. This query will give you customer info of sales transaction: select b.FirstName, b.LastName, a.* from [Transaction] a join Customer b on a.CustomerID=b.ID. Please pay attention to the brackets around Transaction – transaction is reserved word in MS Transact SQL – the Microsoft blend of SQL92
- Hints on dataflow/synchronization – Microsoft RMS uses worksheets technology and all the data goes from stores to headquarters database through worksheets. Headquarters database doesn’t create its own transactions – so be careful and do not try this type of data integration.
- SQL Views and Stored Procedures – yes – feel free to create them directly in RMS Headquarters database and deploy in your Crystal Report.
- Advanced Techniques – in MS SQL Enterprise Manager you can create Linked Server to all ODBC/OLEDB compliant databases: Ctree, PervasiveSQL/Btrieve, MS Access, ORACLE, DB2, Unidata, Navision (C/ODBC) and using OPENROWSET construction you can create geterogeneus view and stored proc – then you can have the data from multiple systems in your Crystal Report.