Use VB 6.0/ADO To Import JEs To GP

[TallOne]

Hi Everyone,
I'm using GP 8.0 on SQL Server 2003. I have another SQL Server running an internet app that creates about 5000 GL transactions a month. I would like to integrate that using a VB6 app(because I'm familiar with VB6). Is that possible? If so where would I start. If not, where would I start? TIA

 

[TallOne]

Well...I'm attemting to use Integration Manager for this and I have a question. My data source is more of a flat file(or not as relational) and destination source is more relational. For example my source table for customers contains all address fields. The destination source contians an FK_AddressID pointing to the address table where those fields reside. How do I handle that? Any comments or suggestions would be super appreciated. TIA to all.
TallOne

 

[stef315]

Are you talking about a receivables or sales integration now? The first post said GL.

 

[jazgeek]

I'd use some sort of an intermediate application to make your flat file more relational. Something in access maybe?


-----------
and they wonder why they call it Great Pains!

jaz

 

[TallOne]

Hi,

Thanks for the replies. Sorry for the late post. I figured most of it out.

stef315,
I was referring to sales, but it seems that I have to do inventory and customers before sales.

As it turns out the examples in IM use flat files also. They just use the same file with different source names and create a relationship amoung them all pointing to one designated as main, based on item number if integrating inventory, cust id if integrating customers and order id if integrating sales.

TallOne

 

[stef315]

That's what my suspicion was...that you weren't really having a problem. I just wanted to know which destination so I could explain the relationship. If you get a case where the debit account and the credit account is in the same row or something like that, that's when you need to "unflatten" the file. In that case, I just used an Advanced ODBC connection as the source file and use a Union All statement.