Thanks for letting me know, Christo. I found that I forgot to include the updated DbDialog.cfg file in the package. Unfortunately, I can't connect to Script Central to upload a new package (a strange problem that has been the case for over a day now). I emailed you a new DbDialog.wepm as an attachment. If it works, I'll post it on my web site if I still am having problems connecting to Script Central.
Regarding Translate Languages, I need a specific example to debug the problem. Jamal On Fri, 5 Dec 2008, Christo de Klerk wrote: > Date: Fri, 05 Dec 2008 16:04:01 +0200 > From: Christo de Klerk <[EMAIL PROTECTED]> > Reply-To: [email protected] > To: [email protected] > Subject: Re: HomerSharedObject runtime error > > Hi Jamal > > I've installed the latest again and tested. Unfortunately neither > DBDialog, nor TranslateLanguages works correctly yet. TranslateLanguages > does exactly the same as when I reported the problem. DBDialog now > produces a different error in GWToolkit. The error message follows: > > HomerSharedObject.vbs - Microsoft VBScript runtime error > Line 726 Column 1 > Object not a collection > > < 0x800A01C3 > > > Best of luck with these. > > Kind regards > > Christo > > Jamal Mazrui wrote: > > That's puzzling. I'll be uploading new versions soon, so let me know if > > the problem persists. Also let me know if the new Translate Languages > > solves the problem you reported (feel free to do so on the scripting > > list). > > > > Jamal > > On Thu, 4 Dec 2008, Christo de Klerk wrote: > > > >> Date: Thu, 04 Dec 2008 19:54:26 +0200 > >> From: Christo de Klerk <[EMAIL PROTECTED]> > >> Reply-To: [email protected] > >> To: [email protected] > >> Subject: HomerSharedObject runtime error > >> > >> Hi Jamal > >> > >> I've got the latest HomerSharedObject and DBDialog scripts installed, > >> but as soon as I press the hotkey for the DBDialog script, I receive the > >> following error: > >> > >> HomerSharedObject.vbs - Microsoft VBScript runtime error > >> Line 703 Column 1 > >> Object doesn't support this property or method: 'oHomer.DBGetFieldLabels' > >> > >> < 0x800A01B6 > > >> > >> The same thing happens on two different machines, my home PC and my work > >> PC. Pity, I would have liked to give the new DBCialog a run for its > >> money, but I'm sure you'll fix it soon <smile>. I've read the > >> documentation and it looks amazing. > >> > >> Kind regards > >> > >> Christo > >> > > >
