Slow Data Entry in EPLAN

Has your installation of EPLAN slowed to a crawl? Are you having trouble with basic data entry? You click in a field to enter some text and it takes several seconds before you can actually enter the data?  In this article I will discuss how to fix this annoying issue that can arise when using EPLAN.

I recently merged several parts databases to form a master parts database, the goal was to simplify my ability to find and use parts data and macros when working on projects. Overall this was a great idea but it did have an unintended consequence; it grew the previously small parts database of 20-30MB to a much larger file of 90-100MB. The result was MUCH more data in my database and the arrival of a very annoying issue, VERY SLOW data entry. Whenever I would enter data in any fields of my parts manager, I could immediately experience this annoying latency.

It turns out this was happening for several reasons; first, my translation database was not properly defined and second, “Translate on input” was turned on and EPLAN was examining every bit of data I typed it and was trying to check it against my translation word list in my translation database.

Lets walk through the solution, the easy stuff first.

Translation Database Settings

Options > Settings > User > Translation > Dictionary

 

Text Input Settings

  • Make sure that Auto Complete (your text) is turned off
  • Make sure that Auto Correct (your text) is turned off

Both of these settings will cause EPLAN to analyze the data that you enter as you enter it and automatically suggest corrections or alternatives.

 

Translation Settings

  • Translate on Input

Turn this off to help avoid having EPLAN suggest alternative languages as you enter text.

Translation Database

Check that your Translation database is properly defined and by that I mean that EPLAN is connected to a valid .mdb  or SQL translation file.
The translation option is an optional module with some lower spec EPLAN offerings and it comes as standard with the EPLAN professional package.
You can define it just like a parts database with only a few minor differences.

EPLAN Translation for MS Access users

For MS Access users you will want to navigate to your default install master data folder typically found at C:\Users\Public\EPLAN\Data\Translation
You may have a sub folder in there with your company name or just a handful of files. We are looking for “Translate.mdb” file

Lets return to your user settings and define the location of your translation dictionary
Options > Settings > User > Translation > Dictionary
Access: Translate.mdb
Or use the […] button to set an alternate path

You are welcome to rename this differently than the default or even create a new on from scratch.

EPLAN SQLand SQL Express users

Setting up the translation db for use with SQL takes just a bit more work, in the case of SQL we need to build the db then import the translation data into it. EPLAN includes data to start your translation database with the install files.

Create the SQL database

Open your settings: Options > Settings > User > Translation > Dictionary

Select the SQL Option

Click on the [ * ] button to connect to your SQL server and create the new database, now may be a good time to ask your IT department for some help. The name of your server will NOT be the same as mine.

I suggest just keeping it simple and naming your database “Translate” or something similar. [OK] to create and close.

You should now see something like this:

 

[OK] to close the settings menu.

 

Translation Dictionary

Now lets establish the data in the dictionary

Utilities > Translation >Edit Dictionary > Management

This should look a bit like the previous user settings screen

Select the “Edit Words” Tab and first check to see if you already have words in your dictionary

For those with a blank database lets import some data, select [Extras] and import

Navigate to your master data translation folder and find “translate.etd”

[OK] and select the languages that you would like to import.

That’s it, your slow interactions should be gone.

Leave a Comment

Your email address will not be published. Required fields are marked *