Blog

MS Access Level required: Medium. Although most systems nowadays are 64-bit by default, it is still very common for Users to have a 32-bit Office installation. One of the reasons could be the smaller footprint by a 32-bit installation, compared to a 64-bit installation, or the cost of upgrading. As a result it is often found that, an MS Access Application based on 32-bit installation that worked for many years, suddenly don’t work when installed on a 64-bit system.

When it comes to automation, MS Access Developers often have to decide between early or late binding, especially when referring to other MS Office applications. The main reason is due to the multiple MS Access versions through the years, 97, 2000, 2003, 2007, 2010 etc. To ensure backward compatibility between versions, it is normally better to use late binding since early binding, could result in non-operation or system crashes because the Library reference made will fail. This article will explained the difference between early and late binding to make the decision easier when doing custom software development.

Your company relies on your SQL Server or MySQL database for your inventory, decision making, customer records, and many other mission-critical components of your business. It serves as the foundation for all of your custom applications and software that keep your company running. But how many companies can afford to have a database expert on their staff? It is just not realistic, nor is it something you need full-time. This is the primary reason hiring a remote DBA (database administrator) is the best option for your business.

If you are looking to add a new database system for your company, you will probably be using either MySQL or MS SQL Server. They are the most common relational database management systems. However, there are some significant differences. The most significant difference is this: 1. MySQL is open-source 2. MS SQL Server is developed by Microsoft.

Could custom software development be just what your business needs in order to thrive? In today’s article, we will discuss whether micro services or monolithic is the better way for you to automate your manual procedures. If you are not sure what those terms refer to, don’t worry. We’re going to help you to know which method of software architecture is more efficient for your company’s clients.

Our company migrated a legacy Visual FoxPro desktop accounting application to a web-based multi-tenant SaaS system using Alpha Anywhere. Using advanced client-side scripting techniques to provide a high level of scalability, the application takes full advantage of the capabilities of Alpha Anywhere as a visual client. Our company has a team of Alpha AnyWhere Software experts that use the latest combination of JavaScript, SQL Stored procedures, and advanced coding practices. In Alpha Five to create user interfaces that are both visually appealing and highly efficient.

Do you use stored procedures? Some developers said, we don’t use it. Too much of a hassle. We would rather use one development tool to encapsulate all in one set of code. I was interviewing a dot net developer for a web scarping project and I asked him, if he can show me what stored procedures he worked lately. I was amazed to realize that the developer has difficulties to identify different features in MS SQL and basically does not work with any SP. He said all is done within the entity framework and LinQ.

In a previous article: MySQL Remote DBA Consultant helped the client to scale up, We discussed a situation where a client had a MySQL server that had 1,100 databases and was using it with a SaaS application. We do not want you to think that having separate databases per client is always a bad idea. There are some real advantages with using separate databases for each client, so we want to go over those also so that you can determine the best way to design your database and structure for your SaaS app.