For support issues and specific questions related to RC-WinTrans' use, features and functions.
02.10.2013 15:34:24
mterzieva
Posts: 2
|
Hello!
We consider migrating to WinTrans 9 but we have old projects (.edb updated from .dll (Delphi stuff)) and it's important that we convert them. However, so far it hasn't been successful.
I put the .edb and the .dll in the same directory.
"File" -> "Migration V7 Database..." -> choosing the .edb file. The migration dialog shows the corresponding .dll file in the "Source files:" part with green ticks under "Exists" and "Up-to-Date".
I choose the target language (since there are a few of them) and click "Start".
Here is the output:
Start RC-WinTrans 7 database migration...
File name: "<filename>.edb"
Adding source file to project...
File name: "<filename>.dll"
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (164): Failed to run the macro. The parameters may be wrong.
Error (401): The file "<filename>.dll" could not be converted to the internal processing format.
Failed!
End of data migration.
I tried also exporting to txt, excel, tmx from WinTrans 7 but for some reason the import of these formats is disabled in my newly created empty WinTrans 9 translation project.
I have a few questions:
1. Could the reason be that WinTrans is installed on Windows 8 and has some VBA problems (I've got the "License error" at startup of WinTrans 9 and installing Visual Basic 6 doesn't seem to help)?
2. If not, could there be a problem with the old projects?
3. Why is import of txt, excel, tmx disabled? Under what conditions is it enabled?
Sorry for the details and, maybe, silly questions, but usually my job has nothing to do with WinTrans, I'm just responsible for converting the old projects.
Thank you in advance!
|
|
0
• permalink
|
04.10.2013 16:17:04
Support
Administrator
Posts: 245
|
Hello mterzieva,
>> Error (164): Failed to run the macro. The parameters may be wrong.
The error comes from the VBA system (the migration is implemented in a VBA macro).
Because you have this "license error" ("Failed to run the macro") from the VBA system
(your question 1 below) this may indicate a problem with the integrated VBA (?) or
VBA components.
Alternatively you can perform the migration manually:
- Open your .edb file with RC-WinTrans 7 and write/create the translated target DLLs.
- RC-WinTrans 9: Create a translation project. Create the target languages.
- RC-WinTrans 9: For each target language import the respective language DLL (created with V7).
- Use the menu command "Files" | "Import" | "Import from Existing Translated File...".
Your questions (1-3):
Q 1.
>> Could the reason be that WinTrans is installed on Windows 8 and has some VBA problems
>> (I've got the "License error" at startup of WinTrans 9 and installing Visual Basic 6 doesn't seem to help)?
RC-WinTrans 9.3:
This error has been reported by a Windows XP user as well. (Re-)Installing VB6 does not help.
We still do not know what causes this "license error."
It seems that this error has come up with the extension of our system macros file "SystemMacros.macro"
(RC-WinTrans 9.3). We cannot reproduce this error but with our previous system macro (from
RC-WinTrans 9.2) there is no error (as fas as we know).
Please try downloading the following zip file and replacing the macroa file in your RC-WinTrans 9.3
installation: http://rc-wintrans.schaudin.com/support/VBAMacrosV92.zip
VBA macros file: "SystemMacros.macro" (S-1914, May 2012)
Folder: .\RC-WinTrans\RC-WinTrans 9 Global\VBAMacros\
To verify the active macro's version numbers use the following commands:
"Help" / "?" | "About RC-WinTrans.." | "Add-Ons & VBA Macros Files" tab
Please replace the macros file in your RC-WinTrans 9.3 installation and let me know if the "license error"
is gone.
Q 2. N/A
Q 3.
>> Why is import of txt, excel, tmx disabled? Under what conditions is it enabled?
Because no item is selected in the list view. Select all the items (Ctrl+A) you want to export.
Note: In the exported files (Excel and TXT) the named column headers are different in V7 and the new
V9. You will have to specify the column in the Import Assistant so RC-WinTrans 9 can import the data.
Regards,
Support, Schaudin.com
.
edited by Support on 31.10.2013
|
|
0
• permalink
|
08.10.2013 14:24:12
mterzieva
Posts: 2
|
Hello, again!
At first sight this fix works like a charm!
No error message at startup, migration process going smooth for old projects, containing around 3k translated strings...
Thank you so much!
Regards,
m
|
|
0
• permalink
|
Powered by AspNetForum 6.9.6.0
© 2006-2010 Jitbit Software