Jan-Erik,

<< Windows Server 2008 >>

I'll have to see about setting up a virtual machine to try that - we're
still using 2003 R2 here live.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote
>
> << Windows Server 2008 >>
>
> I'll have to see about setting up a virtual machine to try that - we're
> still using 2003 R2 here live.
>

Same issue using Server 2003 R2, I checked today.

--
Jan-Erik

"Tim Young [Elevate Software]" wrote

>
> Absolutely not.  Can you send me the database catalog (edbdatabase.edbcat)
> and table (.edbtbl, .edbidx, and .edbblb) that you're using ?  Something
> is definitely wrong, but I cannot replicate it here using the Unicode EDB
> Manager.

I hit the send button 1 minute ago, so it's on it's way.

Could it be something with the Trial's ?

Jan-Erik

Jan-Erik,

<< Same issue using Server 2003 R2, I checked today. >>

Hmm, this is really weird.  I'll have to try it on our server and see what
happens.  I'll let you know what I find out.

--
Tim Young
Elevate Software
www.elevatesoft.com

Jan-Erik,

<<  Could it be something with the Trial's ? >>

No, it's an IFDEF issue.   See my reply to David Michael in the EDB General
newsgroup.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote

> <<  Could it be something with the Trial's ? >>
>
> No, it's an IFDEF issue.   See my reply to David Michael in the EDB
> General newsgroup.

Thanks Tim,
That was quick, the define worked for me as well!

The only thing left now is the MIGRATOR Error #202 problems I have.
(the GAC thing is not an issue for me at all, make 2.0 your #1 priority)

--
Jan-Erik

Jan-Erik,

<< The only thing left now is the MIGRATOR Error #202 problems I have.  (the
GAC thing is not an issue for me at all, make 2.0 your #1 priority) >>

That one is a little more difficult because I can't seem to replicate it
here.  Could you possibly send me the source SQL Server database that you're
trying to migrate ?

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote
>
> << The only thing left now is the MIGRATOR Error #202 problems I have.
> (the GAC thing is not an issue for me at all, make 2.0 your #1 priority)
>  >>
>
> That one is a little more difficult because I can't seem to replicate it
> here.  Could you possibly send me the source SQL Server database that
> you're trying to migrate ?
>

Tim,

I don't think that's where the problem lies, I'm getting the same error just
by querying the MigratorParams table.
I'll do a quick test on Vista and XP, just in case there's something fishy
going on using Server OS's. (althoug I doubt it's related)

Since Unicode is now behaving, this is not an issue anymore, we can catch up
on this later (post the 2.0 release)
But lookout for more issues, I'll start working on this project in a few
days

Anyway, you can expect my order tomorrow

--
Jan-Erik

Jan-Erik,

<< I don't think that's where the problem lies, I'm getting the same error
just by querying the MigratorParams table. >>

In that case it's more than likely that you're still not using the correct
migrator DLL.  The params are loaded from the migrators themselves, and this
is something that should always work because we code them all and there's no
user intervention.

<< Since Unicode is now behaving, this is not an issue anymore, we can catch
up on this later (post the 2.0 release)
But lookout for more issues, I'll start working on this project in a few
days >>

Well, I can't see how you could possibly hit any more issues than you
already have - you hit the trifecta in the first day.

<< Anyway, you can expect my order tomorrow >>

Thanks very much.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:
<<<<
<< I don't think that's where the problem lies, I'm getting the same error
just by querying the MigratorParams table. >>

In that case it's more than likely that you're still not using the correct
migrator DLL.  The params are loaded from the migrators themselves, and this
is something that should always work because we code them all and there's no
user intervention.

<< Since Unicode is now behaving, this is not an issue anymore, we can catch
up on this later (post the 2.0 release)
But lookout for more issues, I'll start working on this project in a few
days >>

Well, I can't see how you could possibly hit any more issues than you
already have - you hit the trifecta in the first day.
>>>

I just received the "download instructions"

I did capture a screenshot showing Unicode all over the place
You'll find it attached.

It also shows another thing I experienced, I happened twice but I can't reproduce. (of course)
Look at the screenshot and notice Mem and CPU used by the server.
My guess would be that it's related to the errors I got while trying to get the Migrator working.

It could have been something close to incident report 2603 as I had to terminate some sessions.

Well, I'm about to download now......

I also want to thank you for your patience and superb support

Jan-Erik