Do you have foreign employees and do you want your Access database to be multilingual?

You have a well-functioning MS Access database application that was created especially for you. The application actually supports the processes within your company perfectly and suddenly the need arises to open a foreign branch. Or maybe you are about to acquire a foreign company and want them to work with your custom application. I would like to take you through the possibilities.

Your Access database in multiple languages, for a consistent user experience

Not so long ago, the director of an existing Dutch customer called. He told me that he was planning to acquire an English and a German company. His only concern was that the CRM application I had built for his company a few years ago was in Dutch.

That was a logical thing to do at the time, since they only have Dutch employees, but now that the takeover plans were on the table, it was a thing. He wanted to be able to follow the business in Engelen and DFuistland as closely as in the Netherlands, but you don’t have to present a Dutch CRM to an Englishman or a German.

The choice was limited; switch to another CRM system that is multilingual and then migrate all existing data to that new system. That seemed like an obvious choice, but where can you find such a package that supports your business processes down to the last millimeter? And how will the employees react to it?
So the choice was actually made quickly. The package we created for his company had to be multilingual.

A fun but also tough challenge. You have to think incredibly carefully about what you will encounter when translating; in queries, reports, forms, exports, etc. etc. And you want to be able to set at user level which language someone should receive. Then find someone who actually speaks the language who can check whether all translations fit the context.

The result is impressive and it works like a charm. During the construction, we immediately took into account that additional languages may be added in the future, so that the intervention is very clear.

A translation plugin for Access

If only it were so easy that, like with WordPress, you could install a plugin to make your entire application multilingual. It doesn’t work that way with Access; you need to create a translation table and then translate all Dutch labels and (error) messages so that you can then call them in reports, forms and notifications. That’s quite a job, but when you see it work, it’s truly magical.

And when we finished that, we realized that there must be more companies that have a similar issue. So if you are reading this and are curious about the possibilities for your Access application, please contact us without obligation. Then we will look at it together and discuss the possibilities.

Meer weten?

Bel of mail gerust als je benieuwd bent of jouw Access toepassing ook meertalig gemaakt kan worden: 06-22716555 of c.keyzer@keyware.nl

Wil je dat wij contact met jou opnemen? Dat kan natuurlijk ook; laat dan hieronder je gegevens achter en we nemen zo snel mogelijk contact met je op

[contact-form-7]

It’s a scenario that happens more often than one might think. A company decides to build or purchase an MS Access application to streamline business processes. The application is developed, often by an internal employee or an external consultant. And then, over time, this expert disappears – either they find a new job, or they leave the consulting firm.

This often leaves the company with a crucial problem: who will now maintain the Access application?

What to do when your MS Access expert is gone?

Lately, I’ve been approached more frequently by companies that have an Access database in operation, but whose creator has retired or left the company for some other reason. Sometimes I get the feeling that Access is a dying breed and I’m some kind of dinosaur. But that’s far from the truth. Access is very much alive and more versatile and stable than ever.

The importance of continuity

MS Access applications, no matter how robustly designed, require maintenance. Operating system updates, new business requirements, or simply unforeseen bugs can pose sudden challenges. Without someone who understands the ins and outs of your application, you could run into problems.

Why I’m the right person for the job

I am an experienced MS Access expert and have assisted numerous companies with their applications over the past 20 years, ranging from simple tweaks to complete overhauls. Here are a few reasons why you should consider hiring me:

1. Experience: I’ve worked with countless Access applications and know the pitfalls and best practices.
2. Responsiveness: When an issue arises, you want it resolved quickly. I offer rapid response times and clear communication.
3. Flexibility: Whether you need a one-time bug fix, a series of adjustments, or a long-term support contract, I can provide a tailored service to fit your needs.

Shouldn’t I commission something new?

It’s a logical question. You feel vulnerable. That Access database is filled with data that’s been accumulated over the years, and there’s nobody who understands how it’s put together. Trust me: starting from scratch to build a whole new application in another language can be a significant hurdle. And then there’s the issue of whether you can smoothly migrate your data to this new application. It’s unnecessary and a waste of the time and energy invested.

Can’t we just continue with Excel?

Possibly. If it’s a very simple database, it might just work. Many businesses first think of Excel because of its accessibility and ease of use. But there are several reasons why transitioning to Excel might ultimately be a bad idea:

1. Scalability: Excel has limitations regarding the number of rows and data complexity. MS Access and other databases are designed for large data volumes and can scale easily as your business grows.
2. Data integrity: Databases like MS Access offer features like relationship management, data validation, and transaction management to ensure data consistency and integrity. In Excel, data can easily be altered or deleted accidentally, leading to inconsistencies.
3. Concurrent access: Databases allow multiple users to access and make changes simultaneously, whereas Excel is more restrictive, leading to potential conflicts and data loss.
4. Advanced queries and reporting: Databases provide robust tools for creating complex queries, generating reports, and conducting in-depth analyses. While some of these functions can be mimicked in Excel, it’s often more cumbersome and limited.
5. Security: Database systems usually offer more comprehensive security features, such as user authentication, access rights, and encryption. Excel lacks many of these in-depth security mechanisms.
6. Automation and customization: With database software like MS Access, you can create custom forms, scripts, and automation processes beyond Excel’s standard capabilities.

While Excel is a powerful tool for specific tasks, it has its limitations, especially concerning advanced data management and scalability. For businesses with more advanced data and reporting needs, downscaling to Excel is genuinely ill-advised. I’ve written more on this topic in this blog.

In other words

Your MS Access application is a crucial part of your business operations. Ensuring continuity and maintenance is vital. If your Access expert is gone, don’t let that be a hurdle.

Want to know if I can assist with modifications, bug fixing, or a support contract? Contact me, and we’ll explore the possibilities together. It’s free and non-committal. You can reach out at +31(0)6-22716555 or c.keyzer@keyware.nl.

Would you like me to contact you? Of course, that’s also possible; leave your details below, and you’ll hear from me as soon as possible.

[contact-form-7]