Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.

Name:
Email:
Subject:
Message icon:
Attach:
(Clear Attachment)
(more attachments)
Allowed file types: gif, jpg, png, txt, tpl, lng, ini, pvd, psf, ini, cfg, csv, zip, xml, pas, 7z
Restrictions: 4 per post, maximum total size 1024KB, maximum individual size 1024KB
Note that any files attached will not be displayed until approved by a moderator.
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What is the fifth word in this sentence?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: nostra
« on: December 02, 2012, 07:13:37 pm »

It is not possible with remote databases, sorry
Posted by: rick.ca
« on: November 17, 2012, 07:48:39 pm »

Welcome.

I don't recall if there's any supported purpose in having a '(dbname).lng' in the DB folder. I always connect to my database via server, and just use 'custom.lng' in the program directory. It works fine.
Posted by: matsja
« on: November 17, 2012, 06:29:28 pm »

Hi!

I can't get a custom language file on a server to work.

It works fine as 'custom.lng' in the program directory and as '(dbname).lng' in the DB folder when you open it as a local database but not when you connect to the database via a server.