Sage 100

MAS 200 V44 PU2. I am trying to create a VI to import data from an ODBC data source (sotamas90). When I try to select the specific table, the system freezes. Since I don't do this everyday, I am probably skipping a step or two. Any thoughts?

Pulling in the sotamas is sometimes very slow.

Sometimes?

Just to display the table? So perhaps, I should just dump the table into Access and then import from the intermediate table.

That's what I usually do or create a pass through query in Access.

I think your ODBC is not setup correctly, this is a basic function. You're not retreiving anything but the data dictionary at this point.

Okay, I'll eat my words. This didn't used to be like this. It finally came out of it after reading 1 GB.

What words are for breakfast? Do they begin with W, T & F?

A process monitor trace shows that much of the time spent is reading.......views.

A distribution of I/O activity shows that during the load of the ODBC tables dialog - 74% of the requests were spend reading views and 0.5% was spend reading the data dictionary. This was an Import job - do people even IMPORT into views? It appears to allow it.

What the heck are views???? After two hours of letting my 200 install read the tables, it is still locked up. Is this a bug??

It's a design flaw.

Views are the pre-defined sets of fields from multiple tables that are suppose to address users that can't deal with linking. I can't imagine ever using them in a IMPORT! I'm not sure it is a flaw more than a bad idea.

Yeah, that's why I didn't go for bug as much as design flaw. I think it's WAD. I think of views as queries in Access.

I see your post on the community. Are you really hung? Do the read counts move in Task Manager? I ran my test locally and it took several minutes.

Like I said in the post, after two hours I killed the job. This entire mission is taking way too long. I was hoping for a quick way to bypass doing an Excel query, saving to a CSV and then importing. Back to figuring out why FRx runs on three out of four Clients WIN 7 32 OS workstations. Opened Sage case this morning. Waiting on a call back (probably tomorrow) from their lone FRx expert......

I was thinking if you could create the import locally then export the job to the system on which it ultimately run. If your counts were at least moving then there's the hope that it would run reasonably locally and be workable.