Having Problem Importing Custom Assy Disc w/2.213 upgrade

flipper · #1 August 1st, 2004, 02:22 AM

Hello -

Just downloaded 2.213 upgrade. Having problem importing Custom Assembly Disc. No matter what I type in for the Disc ID# it will not take it. Hoster is only bringing up what is already imported.

i.e. I type MTU83 and it will bring up the first disc imported that begins with "M" but will not allow me to enter the MTU83. This was never a problem on any of the previous versions. I read the manual but there is nothing that has been changed regarding importing Custom Assembly Discs.

Anyone else encountering this problem? Could this be a bug?

Any ideas?

Flipper

George · #2 August 1st, 2004, 08:51 AM

Flip,
Try importing it under the UNKNOWN BRAND tab, not CUSTOM ASSEMBLY.

Hope this gets it for you.

George

Eric Whitehouse · #3 August 1st, 2004, 10:44 AM

I am having the same problems as Flipper. I cannot import the new Sunfly disc which has just arrived. I cannot get a new Disc ID No - it just goes back to what is already imported. Any ideas?

flipper · #4 August 1st, 2004, 02:01 PM

Tried it under Unknown brand but and it worked however not without a great deal of effort. everytime you type a letter it goes before the previous letter you type. Someone who was importing their discs for the first time wmould be very frustrated in a very short period of time.

I think that this is a bug that should be addressed.

So far everything else is working as it should. Great Job MTU!

Flipper

George · #5 August 1st, 2004, 02:40 PM

Yeah, you're right Flip. I just tried it in UNKNOWN BRANDS with the same results, program transposing entries.

George

Eric Whitehouse · #6 August 2nd, 2004, 08:00 AM

Hi,

I'm still having problems importing the above new disc. My symptoms are the same as Flippers. Is this a bug or am I doing something silly ?

Eric

George · #7 August 2nd, 2004, 10:05 AM

It is being taken care of. Thanks Flip for finding this. I've reported it on the Beta Forum, and Admin has confirmed.

George

**admin** · #8 August 2nd, 2004, 03:58 PM

We verified this was a bug when importing with ANY Brand, not just Unknown or Custom Assembly.

The problem turned out to be the new feature we added that automatically incremented the BookID. The Brand-DiscID-BookID fields are so intertwined that a simple change broke the DiscID field. We reviewed the code for hours and understand what is happening, but can't find a simple way to fix it.

As a result, we have removed the new Auto-Increment on the BookID field so it works like 2.212 and prior.

We now have a new 2.213 Release #2 available for download. Please click your Hoster download link to get it.

If you want to do some importing right now, you can enter the DiscID BACKWARDS

.... and it should work. However, we'd rather you download the new to make sure some other bug is not lurking. This is one that got past all of us!!!