1) Which Microsoft products do you work with?
We work with all versions of these Microsoft development tools:

• MS Visual Studio .NET
• MS ASP.NET
• MS SQL Server
• MS Access

We also integrate these Microsoft applications:

• MS Office (Excel, Outlook, PowerPoint, Visio, etc.)
• MS InfoPath
• MS SharePoint
• MS Great Plains
• MS Office Accounting

2) Do you only promote Microsoft products?
No. Not at all. I promote and I'm experienced in MS because most of my customers are using Microsoft. So it's an easy array of products for me to get behind. However, I do promote alternatives if appropriate to the project, such as Sun Microsystems Java, and use all sorts of other products in conjunction with MS products.

3) What products have you integrated with? QuickBooks?
We have integrated large and small applications into existing or new systems, including:

• QuickBooks
• MS Great Plains
• MS Office Accounting
• MS SharePoint

System integration is a real time saver and helps eliminate double-entry of the same data, reduces errors, and speeds business. For example, I integrated QuickBooks for a customer that was ready to move away from paper invoices. We set up everything to transfer between the customer and their vendor, so invoices are now received electronically (via EDI) and the data automatically populates QuickBooks.

4) Is Microsoft Access the right solution for me?
Microsoft Access is a rapid application development (RAD) platform for databases. We develop data driven software in many computer languages, and I have yet to find a platform that is faster and easier for database application development. Plus, many developers don't realize its great power for its low cost.

I hear some people say that "Access is slow and doesn't scale." This simply isn't true. I have been called in to fix many database performance problems. With Access, the most common problem is the previous developer's poor design skills. What some developers don't realize is that Access can be used as a standalone database, or, as a "front end" to a larger database, such as Microsoft SQL Server. "Microsoft Access Projects" communicate directly to Microsoft SQL Server. This is a very efficient and secure means of storing data; it's much more efficient that trying to use a file-based Access database by itself. Plus, since Microsoft SQL 2005 Express is free, why not take advantage of it. I have customers with more than 40 simultaneous users, connecting to a server with Access, SQL, Exchange, file sharing, print sharing, and Active Directory installed on the same server. No performance problems.

5) What rules out using Access as my development platform?
The following 3 considerations may rule out Access as your solution:

1. Remote Users: If you have a large number of remote people that need to view the data, an ASP.NET web application may be a better solution for you. It depends on your needs. I have customers that use an Access front-end internally in the office, and have a small ASP.NET web component used by remote sales people that only has 10% of the functionality of the internal Access application. Terminal services can also be used to view Access applications remotely in some cases.
2. Simultaneous Users: Another limitation of Access is the number of simultaneous users that can use the system. If you purchase a server dedicated to just Microsoft SQL, with multiple processors, 64-bit operating system, and plenty of RAM, you will get 80 to 100 simultaneous connections to the database without much problem. If you needs are any larger than that, a .Net application will likely be a better option.
3. Application Size Requirements: The last limitation of Access is the actual size of the application itself. While, yes, you can create an extremely large application in Access with hundreds of forms, it really doesn't make sense. Access if perfect for smaller applications in that they can be built quickly and full of functionality. If the application becomes very large, Access becomes more difficult to maintain. You would benefit from using an enterprise-level application development platform. The only "real" choices in this arena are the Microsoft .Net platform, and the Java Platform Enterprise Edition. Applications built in these platforms, are much easier to maintain when the application becomes large. There are many other developing platforms on the market, but among the majority of serious business application developers, these are the only two feasible options on the market for large applications.

We've had multiple instances of customers wanting, and starting, with a small Access application only to realize the power of the software in transforming how they do business. What generally happens, is that customers get a taste of how powerful the technology is once they have it in their hands, and they start coming up with their own ideas on how to bring it to the next level. In these cases, we end up re-developing the front-end Access application in .Net or Java to handle the larger application size.

6) So you do software, what about hardware?
Software is my main focus, but I'm involved in hardware products if they are needed to help make your system work.

Hardware used to be more central to my work so I have a complete hands-on understanding of server and network hardware and have built many networks from scratch. This helps me better understand your software project in context of your existing system. It also helps me troubleshoot problems.

7) What about product integration with peripheral devices like mobile phones?
We have experience in integrating all sorts of peripheral devices such as mobile phones, cameras, scales, and electronic signature pads.