Error when entering items, #temp, error already an object named" # "temp" in the data

[Angel Vazquez]

Error already an object named" # "temp" in the database

Problem:When entering items you receive the above error message
when trying to save.

Who is affected? This error can happen to customers who have been converted from Liberty for Windows, Stoker, Consignment Boutique, or just updated to Liberty 4 consignment 3.5a.

Workaround: When this happens again look at the inventory list and click on the item number column name to organize the item numbers in ascending order. Once you have done this, scroll to the very bottom of the item list to see what the last item number is.Now you can increase the number in the "next item field" by one above the highest item number shown in the inventory screen. This will ensure that after 3 or 4 items you don't receive the same error on this account again.

This issue has been submitted to Development and we hope to have a fix on a future release.

Let us know if this helps!

Angel Vazquez
Liberty Support Specialist
Resaleworld.com
888-229-0096

[Support Team]

We've just been handed the initial builds of the next release (tentatively 3.5d). This release will address the following issues:

- 534 errors on multiple reports (all stemming from a few, common areas)1
- Report "Preview" screen (within Liberty Inventory and POS) pulling correct dates
- "On" and "Between" Criteria controls no longer "vanishing" after clicked
- Roll-ups from 3.5a follow-up patch
- "Remove item from Storefront" hooked in
- Can no longer "break" and item's association with reCommerce by removing its Marketplace
- Auctions ended on eBay will no longer reflect in your reCommerce store
- Front-page Category images officially launched
- much more!!!

We're anticipating a release by the end of March, pending Alpha and Beta testing. If you're interested in getting your hands on a Beta copy once it becomes available, post it up here on our Message Board in the Beta Testing Area (http://forums.resaleworld.com/forumdisplay.php?f=119).

[debmcd]

I also hope the issue of "pulling" client names for mailing labels (with certain parameters) will be fixed.
We have not been able to send out birthday cards to customers for the past few months..............:confused:

[Support Team]

There definitely were some adjustments to the Mailing Label reports. Customers that converted from LFW weren't able to pull all accounts - until they entered an email into the account and saved it (weird, I know).

The queries are new and thus, look for new data such as email addresses. Accounts from LFW would never have this sort of thing and thus, wouldn't appear on this report. We've made that query a little more forgiving and have resolved that specific issue.

If you can let me know a little more about your issue Deb, I can take a look and see if this is in fact covered in this next maintenance release. Keep us posted!

[debmcd]

we also use a date range when printing labels-say all birhdates from 1/1-1/31 or paurchases made w/in 1/1-3/31.
The new program does not recognize these dates-it wants Jan or March from what i understand from support. nelson was able to give me a "work around"
that worked for awhile but now I can't get it to work.
Any idaes? I need to do a major mailout for our 17th anniversary late april.

[debmcd]

I tried again w/ the work around Nelson had given me and it worked this time! Hooray-now my April birthday clients will get a card. :D