Perhaps a more direct approach is needed!

It’s also a lot faster. Orders of magnitude faster, in fact, than the old version (1.0). I’m very happy with it! The project has become proof to the owner that This is the way to go after all – a staged complete conversion of all sites to their shiny new Mac OS X Snow Leopard Server running both the database and the web application(s).

Unexpected internal c-tree(R) error #7495 (uerr_cod=0)

That’s the error message I was getting one day. Nothing major happened, the update routines just stopped working on day!

I’m importing a bunch of data from the usual tables (CustomLists, Customers, Items, Sales) in to the SQL Server back end for faster processing against the company’s CMS. I do this because of the way MYOB has done it’s ODBC driver, every time you do a query, all the table records are read in to memory and THEN the filters are applied, it’s horrendous. Especially if, like this company, you have upwards of 100,000 sales lines. So anyway, it happily dumps the data into the SQL Server tables (using MS Access 2007 as an intermediary) without issue.

The error occurs when I start to insert new records in to the MYOB file.

I’ve tried using the same connection (Reading from a RW connection). I’ve tried using a two connections (Reading from a RO connection and writing to a RW connection); to no avail.

The solution?

ONLY read from or write to the MYOB file while the connection is open. I have taken this to the extreme and put a switch in at the start of the run; if it’s 4am – write any new sales to the MYOB file; if not – read all the MYOB details and update the CMS accordingly.

The error is gone and the work flow is easy to understand for the staff:

• Each morning new invoices should be in MYOB and;
• During work hours the payment details entered in MYOB will be reflected in the CMS every hour.

Obviously the memory handler for the underlying database couldn’t deal with the large number of rows being returned.

Update the booking system(s) with the latest payment information from MYOB.

Why do we do it?

The company does not want to service customers that are not paying their account.

Who is responsible?

• Automated Task Scheduler process on IWM-TS-001.

When

• Every hour, on the hour, between 6:00am and 6:00pm
• Booking systems that are live: [Instant, Bunbury, Northwest, Ace & Mandurah]

How is it done?

1. Import MYOB data via MYOB ODBC link (myob_sync.accde)
   1. Import MYOB Items details into booking system
   2. Import MYOB Customers details into booking system
   3. Import MYOB Sales information into booking system
2. Execute processing routines on the SQL Server
   1. Compare product codes
      1. Match product_options.myob_code => imported_items.Item_Name
      2. Email ([settings].[sync_notify_email]) the list of item codes that are missing from MYOB
   2. Compare Customer information
      1. Match customers.name => imported_customers.company_name
      2. Email ([settings].[sync_notify_email]) the list of Customers missing from MYOB
      3. Email ([settings].[sync_notify_email]) the list of Customers with different addressing details
   3. Update payment information
      1. 1. Copy details from MYOB_Sales –> imported_invoices table
         2. convert all the numeric invoice numbers to long type
         3. Remove records that didn’t covert to long
         4. Match imported_invoices with existing invoices and save their details to tblToBePaid
      2. Clear all agreed payment dates that are in the past (the agreement has expired)
      3. Update account status for all customers
         1. Customers who are over due but not on hold => put them on hold
         2. Customers who are on hold but no longer overdue => take them off hold
         3. Add a message to any client that has been switched saying why it has been switched (Account Paid, Automatic hold)
      4. Set any held customers with “agreed payment dates” to off hold (they have agreed to pay us, but the date has not yet passed so we should not break our side of the bargain)

Important Notes

• This system will operate well as long as the Account Notifications procedures are followed by staff.
• Occasionally the myob_sync.accde file is renamed Database.mdb for some (unknown) reason. This stops the scheduler task from running correctly, so I have added a MYOB Sync Fix step to the schedule, which should resolve the issue for the moment.

After a little searching I found this:

INSERT INTO
    target_db.dbo.sysdiagrams
SELECT
    [name],[principal_id],[version],[definition]
FROM
    source_db.dbo.sysdiagrams

Just change the target_db and source_db labels and it will bring everything across. Obviously there are further refinements that could be put in the query, but the basics are there, extrapolate as required.

The Online Job Cards system is integrated directly into the existing legacy booking system, providing a fast reliable link between the drivers performing the services and the operations staff overseeing each division. General job status is provided visually using colour coding on the operations mangement screens in real time. When a new job is allocated to a driver, it will appear on their mobile device as soon as they refresh their Online Job Card.

Another excellent situation for data enabled mobile devices. Further updates are planned, including obtaining customer proof-of-completion signatures for invoicing purposes and using Location Services to pinpoint where the jobs are being performed.

This solution uses:

• Microsoft SQL Server
• Ruby on Rails
• Telstra NextG
• HTML4+ enabled web browser (iPhone/Android/iPad)

The solution needed to replace and expand upon the existing system that had reached it’s user limit. All the existing functions were replaced/recreated before creating additional functionality. A new series of detailed financial reports allow for reconciliation and fast data entry into the accounting package; instead of entering individual transactions for each member the client is now able to make summary transactions for the total amounts to be allocated to their different destination accounts. A date driven approach has allowed for continued expansion of payment methods, specifically direct payment via internet banking, without compromising the traditional collection process.

The solution is complete, occasional development of new functions is undertaken when the clients business model changes. In fact, the system has been so popular it’s now being used by quite a few affiliated associations in the south west of Western Australia and Tasmania.

This solution uses:

• Microsoft Access 2007

Supplying allied health professionals to locations in Australia and New Zealand. The database tracks members from all over the world (Australia, Ireland, New Zealand, South Africa and the United Kingdom to begin with); their current qualifications; future plans; visa arrangements; and local accreditation progress. Placement officers are constantly in contact with candidates and clients throughout the day so data entry must remain a simple process. The search form allows for very detailed criteria so that the least number of enquiries can be made while finding candidates who are available, and interested, in the position.

This system has recently been migrated from an Access 2007 back end over to SQL Server 2008, the process was done in-situ over a period of weeks (and while it was being used in a live environment!). A more detailed search function is being investigated, along with increasing the list of details being stored for clients and candidates.

Technology used

• Microsoft SQL Server
• Microsoft Access 2007

I have worked with Access 2007, 2003, xp, 2000, 97 and even 2.0!

I also have a solid understanding of SQL Server 2005/2000 and have built/maintained/improved upon many enterprise level systems.

Naturally, I wanted to put it on facebook to allow others to do the same and to encourage people to “race their friends” to their body composition goals.