Sage 100

ODBC driver. I am working on a WO custom report. I am trying to run using data in a test company. I am within Crystal, report has not been put on a menu yet. The ODBC driver is pointing to live company, so while I add a dupe copy of each of my 3 files (CI_Item, CI_ExtDesc, WO1) and change all of my formulas to use these files instead (and have logged in to the test company when adding those files). The report is working as I then start to take back off the OLD files, but when I take the last one off, the fricking thing reverts back to using the live company. What, exactly, GIVES with the new ODBC and the strings that hardcode company codes, and all that crap? I am using the SOTAMAS90 driver that SHOULD be working as it always has, but now it seems to be hardcoding login stuff, too. I suppose I can start totally from scratch on this, but it is a label report and you all know how picky labels are. Can someone just explain to me how the ODBC driver works and what I need to do to get it to use a different company like it used to do?

I am under the assumption that once you connect to a company, it remains that company. have you tried saving the report and closing completely out of Crystal, then start again forcing a new connection? I by no means am a Crystal Genius, however. @ThereseLogeais ???

Yeah, I always thought it would stay that company you were connected to, as well. But no. Maybe because I have a non-framework file? Grrr.

Beth, if you are seeing the long string with the company code and all try going to Data Base > Set Data source location in the bottom window select the SOTAMAS90 driver under my connections, log in to the test company then highlight each table in the your top window and the same table tin the bottom window and click on UPDATE

David - did that. :-(

I thought you probably know that little trick, I'm not sure what would force it to revert back to the other company. Sorry it's not saving data with the report is it? maybe that is causing weirdness?

No. I mean I was previewing it with the new CI_Item, CI_Ext Desc and both WO files and it was fine. Then when I took the OLD WO file off (which was stubbornly connecting to the live company), POOF! The new stuff disappeared and I was left with just the live company again, even though the file I was using had supposedly been logged into the test company. ARGLE. I know I'm going to have to start from scratch. *&^$%^%#&^%#

Just an idea, create another DSN for Sage with a different name and see if that works. If it does, I'd delete the original DSN, reboot, and re-run workstation install so it writes the DSN again for the default.