Not sure if anyone here can help or not but thought I'd give it a shot. I have a call into BSI support but they seem to be extraordinarily busy today.

I am following the BSI document "Instructions to upgrade from TF7.0.x to TF8.0.x".
I have performed each step per the document:

1) Backup custom data using the Tech Tools (selected the TF80 option)
2) Ran the sql script (after downloading and expanding the server .exe file) to
create new tables in the new database (oh yeah...created a new
DATABASE..would have been nice if they had included THAT little step for us
newbies!!!!)
3) Created a new ODBC connection
4) Install the TF80 client
5) Execute TF80 on the appserver...and as soon as I log in, I get this error:

5110 - NO DATA_SET_ENTITY CURRENTLY EXISTS

As I said, I have a call in to BSI support, but so far have not heard anything, so any help is most appreciated!

I mentioned the database creation in my steps because they don't include it as part of their documentation. :P

When you installed the TF80 client did it ask you to create a new ODBC connection or did you create it before that?

Open your registry editor from run->regedt32 and paste what you see under

\HKEY_USERS\S-1-5-21-1496332988-1757221872-1847928074-1151\Software\BSI\TF80\Connection

for the key DSN. Like I mentioned the Taxfactory client hates not having it's way.

Yes - I was following their Instructions document. I really couldn't follow your steps (at that time anyway) because I didn't know enough about the process. ("Base data" and "Reg bulletin" meant nothing to me - I TOLD you I was a newbie!!) :-)

As I got thru each step, I learned a little more, but honestly the very first step I had to call support. I have never had my fingers in this stuff before so most of their documentation is just not that helpful.

I finally did get support on the phone, and I had to create a new dataset, and a new environment variable - and those steps took a while for support to figure out. Absolutely no way to get this from their "how to". How would I have known what a "master file" is??? Do they discuss what that is ANYWHERE?? Nope.
Very frustrating. Oh well. I'll get there....but it sure is a slow process. :-(

Yeah, it took me a while reading and re-reading to figure out some of what BSI was telling me. I kept looking for the "master file" and finally contacted BSI. That's when they said they would make it available for download for a short time before it disappeared from their website for me.

As for the dataset - you shouldn't have had to create a new dataset. I have kept mine at default and it's worked fine.

You used the Default one??? Hmmmm. I think they had me create another one because they were also looking at the Lawson docs and wanted to follow that naming convention. So if you used the Default, what does your system variable look like? DATASET = DEFAULT?

By the way - when you restore the Custom Data...you choose the existing dataset, and then accept the default settings on that screen?? Can't get support to respond so I'm sitting on my hands here!!

Where you say to modify the Lawson.env file...where does that file reside?

Lawson instructions say to add a 2nd new system environment variable called TF_CONNECT_STRING, with 4 pieces of information. The only system environment variable I know how to create contains only 2 values - the variable and the value. ???

Never mind. I just realized that you enter the entire string in...duh.

How did it go?

Sorry for not posting back earlier! I did get the BSI upgrade completed...in TEST at least. But I never have found a lawson.env file...it does not reside on either server (app or web) so not sure what the impact of that is. If anyone knows, please clue me in!!

Yeah. I'm wondering if that's just UNIX thing then. The lawson.env file in UNIX is where all the environment variables for Lawson are defined. I don't know then where it would be defined in windows.

Yep...it IS a Unix thing. When I read the Unix sections of the Lawson BSI Integration doc - then it made sense. Variables are simply added in a different manner on the Windows servers.