Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
filf
Yak Posting Veteran
67 Posts |
 Posted - 2002-06-28 : 09:14:40
|
| If so I would like to know how to do this, I understand that table linking created within access uses full unc paths. So if I place my db on a webserver the table linking is going to die.I have played with automation quite a bit in an access runtime environment, but now need to do something similar to this for web pages. In my scenario I need to be able to compare records in one db table, with records in another db table.I need to do this record by record, there could be a simpler way of doing what I need to do by seperating out the logical processes involved. (any ideas about recordset comparison that do not have processing overheads?)To provide background, I have a number of databases which are used purely for logging, the reason I keep them seperate is that I can download one smaller db file at a time without having to download massive db files. These logs contain contact details for people coming through our site and also contact details about registered users of our software. Quite often we need to contact these people so b4 mailing these users we need to compare a log with our centralised unsubscribe system, this is where the seperate db comparison comes into play.Also due to script timeouts etc, when sending mails I need to keep a centralised log of who has been sent a mail just in case the process dies so that I can resume where the process dies.If we had our own box we could use sql server and actually not have any of these issues, but cos the boss won't pay I am saddled with access.Any thoughts, ideas suggestions regarding this would be greatly appreciated. |
|
|
filf
Yak Posting Veteran
67 Posts |
Posted - 2002-06-28 : 10:49:39
|
| Just done a test with the linking tables method, as I thought, it failed totally.Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access Driver] C:\someUNCpath\test\dbB.mdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. Guess the next option is automation via asp, having an admin at the other end link the tables for me is not going to be workable.Wish we had our own box. |
 |
|
|
Doug G
Constraint Violating Yak Guru
331 Posts |
Posted - 2002-06-28 : 20:11:15
|
| Once I linked access DB's on a remote server. You have to either write some code to do the equivalent of the Linked Table Manager, or create an identical physical drive structure on your local machine, link the tables, then upload to your server. If the paths are identical the links still work after you upload.======Doug G====== |
|
|
|
filf
Yak Posting Veteran
67 Posts |
Posted - 2002-07-02 : 04:50:02
|
| I have found a way simpler method of doing what I was trying to do and it works beautifully, it is a sql based solution.SELECT * FROM table_name IN 'otherdatabase.mdb'Using some sql along these lines embedded in a sub query allows me to pull a recordset which spans two totally seperate db's.I found that using full paths to the db file gave me excellent results.sqlstring = "select * from test1 where test_id in (select test_id2 from test2 in '"&server.mappath("/test/dbB.mdb")&"');"rs.open sqlString,objConnI had coded an ADO dsnless db connection to the first db [dbA] and even though dbB sits in the same folder as dbA I reckon the full path is the safest solution.Cheers. |
|
|
|
|
|
|
|
|
Can automation via asp link tables in seperate dbs