Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CR XI - Exporting to ODBC??

Status
Not open for further replies.

OrionStar

Technical User
Dec 3, 2004
336
US
Ok, I hope this is not a silly question, but I'm trying to export my data using ODBC. The window pops up and I assign a NAME only to the file. The process happens quickly and looks like it finished.

I just have one question....WHERE DID IT GO, WHERE IS IT? I cannot find my DB?

Help.


Thanks:
Mike Vega

"What would you attempt to do... if you knew you could NOT fail?
 
It created a new table in the database that is used by the ODBC data source you selected.

Cheers,
- Ido

Visual CUT & DataLink Viewer:
view, e-mail, export, burst, distribute, and schedule Crystal Reports.
 
Sorry guys, I should have looked deeper before I asked, I'm just under some pressure here to produce some data.

Anyway, I found some reference material here...so nevermind...I'll try this first and be in touch if need help

thx

Thanks:
Mike Vega

"What would you attempt to do... if you knew you could NOT fail?
 
OK, I'm beginning to understand. I just used some reference threads from you to someone else and created a .MDB DB shell and am now exporting my data there.

I've exported my report into a .MDB db and now I'm using this to link to my report. According to what I calculate it IS going faster. I estimate that it will take this report 3.75 hours to run/process. This is as compared to the over 16 hours and then some before.

I'll let you know what happened and if all balanced out. Believe it or not for all this YTD data I can live with 3.75 hrs

Thanks:
Mike Vega

"What would you attempt to do... if you knew you could NOT fail?
 
Linking from Access to external ODBC tables would be much faster (and less complicated) than the approach you are taking.

Crystal ODBC exports are limited to new tables (if the table already exists, the export fails).

hth,
- Ido

Visual CUT & DataLink Viewer:
view, e-mail, export, burst, distribute, and schedule Crystal Reports.
 
Man O Man.. I have to tell you something.. the whole reason for this attempt at using .MDB was to try and combine data from one server to another.

We have outsourced our DBA and just so happens that he is here in the office today.

He just copied my INTERSYSTEMS ODBC data tables OFF of that server and placed them onto the SQL SERVER.

WO the report that was taking hours and hours.... (actually over 16 hours) to process, is now taking.... 5 seconds...........FIVE SECONDS...

I'm completely amazed.

problem fixed.....for good....thanks


Thanks:
Mike Vega

"What would you attempt to do... if you knew you could NOT fail?
 
I trust the DBA didn't just "copy" those tables but linked them as suggested in my original response. Copying would mean that you need to repeat the copy process since the data keeps changing. Linking means that SQL server treats those remote external tables as virtual local tables.

Cheers,
- Ido



Visual CUT & DataLink Viewer:
view, e-mail, export, burst, distribute, and schedule Crystal Reports.
 
We are having a job created to "copy" the tables (4-5) tables in all over from the INTERSYSTEMS CACHE server to SQL server. The files are very large, but the whole process takes about 17 minutes and can be completed in the late night hours.

Another goal was to take the tables OUT OF PRODUCTION, that is so that these can only be used for reporting purposes.

The data will be updated every night...and so current data will be reported on each day.

I'm elated... you all have probably seem me posting here trying to seek answers to my slowness.. but it seems that my problems have been solved.....or at the very least reduced greatly... I'll finally be able to move forward and get some things done.

Anyway, that is why we are not linking. Does linking keep those tables in an ACTIVE type of status so that when people are writing to the original tables, that they are locked out so to speak? This is what we are trying to avoid.

I don't think we need LIVE tables, and the overnight update I think would work just fine...

Lightspeed is awesome.....



Thanks:
Mike Vega

"What would you attempt to do... if you knew you could NOT fail?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top