ForumsTechnology Management

I have two clients that use Access for action tracking, but I'm not a big fan. The database seems to corrupt rather easily when opened by other apps or multiple users, and I've seen automatic updates on end-user platforms create some messy compatibility issues.

It doesn't sound like you need a solution that's as complex and pricey as SAP Business One, but I wonder if something like Intellisoft's ManageMore might be the type of alternative you're seeking (I don't have any connection to them -- it's just an option I'm aware of). I know their database is open source (which would make transition/migration from your existing system easier), there's an integrated suite of functional applications in the package, and the price seems reasonable for a small enterprise (perhaps less than the cost of rebuilding the system yourself, or hiring an expert to analyze, recover, and repair your existing system).

You may have specific business requirements that make this a poor fit (or a great one) off the shelf . . . but it does sound like your business may have "outgrown" the proprietary solution you have now, and that a revised system built around Access may still not provide the long-term results you want. Whatever option you choose, best of luck!

You might want to try doing an "upsize" to SQL Server, and see if that stabilizes the system.

Aside from that, the right thing to do is analyze the current database, apply any "quick fixes" to make things faster, then, try to rebuild it. The process of rebuilding should happen in parts -- break the big app into parts, and rebuild each one.

I'm generally against "big rewrites". Your system has probably accumulated features, and possibly contains data that doesn't really conform to the original data structure. It's easier to preserve these features and data if the new code has to interact with the old code and data.

If you have expansion plans, then, the app will probably factor into the tables (in an external DB), code modules, reports (probably in HTML instead of Access), and the Access forms. The intention (most likely) will be to glue these parts together with VB.NET or C#.

I'm working in an app that's not really being refactored, but is being expanded via exports -- data is being shuttled out of the database into Outlook and text files, so more people can use the data. Later, I'm going to try and publish data via web pages. My situation is that one user likes Access, and everyone else isn't into it. To increase usage of the data, I have to make it work for everyone else.

I have mapped out the flow of information to and from tables. Have also taken screen shots and copies of forms and penciled in the changes that I would like. Have approached this from the stand point of what I would need if my business increased by 500%. This way there will be plenty of room to grow and should flow smooth during that time.

Part of the complication is that I have macros embedded that work with Corel Draw and they are the most unique part of the db. These drive the production process as they create the production runs and create the new personalizations. These new personalizations are then saved for fututre use.

Jim

Can you move the macros into Corel Draw, and then call them from Access? Lighten the load on the db side, and it'll be a smaller project.

Yes, I did put the macro into the flow chart. That macro is the brains of the outfit as it makes things really efficient.

I interviewed 3 db people yesterday for doing the work. Thanks to all of your suggestions I was able to talk like I knew something. I was surprised that of the three, only one googled me. So that's the guy that I went with as he knew when he walked in the door what I did.

I am going to stay with Access for know and just fix the errors. Then get into making changes to some of the forms and data flow.

Jim