![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Are there tools/techniques/objects to map Universe data to SQL? I have a Universe box and a client with SQL. This is my first exposure to dealing with "flatness" online. I know how to convert data, but I thought there might be some interface which could model/map it on the fly. |
#3
| |||
| |||
|
|
On 2011-02-03 21:18:46 -0500, "Ed Sheehan" <NOedsSPAM (AT) xmission (DOT) com> said: Are there tools/techniques/objects to map Universe data to SQL? I have a Universe box and a client with SQL. This is my first exposure to dealing with "flatness" online. I know how to convert data, but I thought there might be some interface which could model/map it on the fly. Hi Ed, The wording of your question leaves me unsure of what exactly you're trying to do for your client, so this may not be the answer for which you are looking. Many version of SQL RDBMS allow for very fast bulk loading of data from delimited files (i.e. csv). I've often found using that facility the easiest/fastest way to move data from MV to SQL. -- Kevin Powick |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
I am being a little cryptic to protect the client, but what I am seeking is a way to have both databases co-exist, and exchange data in a live fashion. I remember when I was using Advanced Revelation, they has a feature called "envitonmental bonding," and I could actually bond to a dBase file, and it appeared just like a Pick-style file. Is there some mapping "object" which I could employ to do a live connection, and have the two (Universe + SQL) databases communicate through a standard (BASIC) language? We're just trying to see if we need to toss one database or, more desirably, use some intermediary to allow a free exchange of information without too much reprogramming on either end. Ed |
#6
| |||
| |||
|
#7
| |||
| |||
|
|
Ed, if this is the company I'm thinking about, we had a tool for a homemade solution about a year ago. *Someone decided not to use that to create a DIY solution, and to go with another more expensive option that supposedly did the entire job. *I'm guessing that didn't work. Might it be time to revisit that? *You've read my blogs and we've exchanged emails. *You know what's possible. *Is there something different about new requirements for which the old solutions are not suited? If you look at one of my recent blogs on extensions for mv.NET, you'll see I've written simple method calls which generate complex ADO.NET data objects from mv.NET objects. *This sort of thing can be used to easily query MV with a Call to a BASIC sub, convert the resulting data to a relational data table in one line of code, and then pass that data to a relational DBMS using whatever mechanisms are available, generally SQL query or stored procedure. I don't think that's exactly what you want either. *The point though, is that the tools exist for creating solutions fairly quickly which pretty much fit any requirement. *For example, I can use the tools in my kit to create a BASIC to SQL interface exactly as you describe, perhaps with no requirement whatsoever for code to be written outside of BASIC. *Unless I see demand for this, I can't jump to creating such a solution, but if I can do this kind of work for a client then it can be productized afterward for everyone. Best to you, T "Ed Sheehan" wrote: I am being a little cryptic to protect the client, but what I am seekingis a way to have both databases co-exist, and exchange data in a live fashion. I remember when I was using Advanced Revelation, they has a feature called "envitonmental bonding," and I could actually bond to a dBase file, and it appeared just like a Pick-style file. Is there some mapping "object" which I could employ to do a live connection, and have the two (Universe + SQL) databases communicate through a standard (BASIC) language? We're just trying to see if we need to toss one database or, more desirably, use some intermediary to allow a free exchange of information without too much reprogramming on either end. Ed |
#8
| |||
| |||
|
#9
| |||
| |||
|
#10
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |