Sage 100

4.10 to 4.50.4.0 upgrade. VI Export jobs are exporting a delimited file with nothing but the delimiter (comma). No data. ODBC security is turned off. The happens with any file. Very bizarre. I've never experienced this before. Anyone else seen this?

Is this after you rewrote the jobs?

Yes. As part of our troubleshooting we created new simple exports from different modules. It happens consistently. All we get are rows of commas - one line where each line of data should be.

When you say simple exports - do you have a select on it?

Sounds like your data dictionaries are not quite right. Can you force a rebuild?

No. When I tested with a select, no records would export because it saw no data. The preview also shows no data exporting, although 100% successful. Tried with ABC.

Try copying the data over to another company and then try and see if it works. What file data are you trying to export?

@JeffSchwenk Rebuilt them - tried that first - no luck. @DianeRuth Used the ABC company as a test - happens with any company. Just got off the phone with Sage Support - they said the data dicts are probably damaged. I will reinstall tonight and let y'all know. Thanks everyone.

had this happen to me once and the only fix was to reinstall

I had it happen in Crystal one time - only no tables appeared. I believe a reinstall was what I did.

Did ODBC security become active by chance?

That wasn't it in my case. I think I actually went in and looked at the file and there was something amiss. It was a decade or so ago so don't ask me what it was. I even had someone I knew from Crystal Decisions on the phone and he said something like, ""Well, I don't really do MAS support but it sounds like there's something wrong with the dictionary"" after which, I called Sage (or was it Best then?) and I'm pretty sure we reinstalled.

Are there any UDF's in the table you are trying to export? If so, did you update the tables?

Bill please post the steps you use to fix this when you know.

Fixed. Reinstalling on top of the existing MAS90 did not work. So I tried a clean install of MAS90 with the ABC company, created a new export job and it worked. So far so good. I then migrated the data from the live MAS90 to the fresh install. VI broke again same issue as before. Recompiling jobs had no effect. The last thing I tried was to create a 'new' export and this time it worked although the existing jobs still did not - go figure. So I ended up deleting ALL the Import/Export jobs and recreating them. They all now work.

So you ended up rewriting all your jobs in your original migration folder? If so, how did rewriting them a second time work when the first rewrite didn't? Very bizarre, but then, that's Sage 100 ERP for you......

Does it seem rewriting the exports ultimately did it?

@WayneSchulz. Yes, but only after removing VI and then reinstalling it. Rewriting the reports originally did not work.

So the moral of the story is? Migrating data broke the V/I install or data dictionaries? I'd like to see how you bill that one.