catalyst2 community forums - View Single Post

IanStevenson · 16-08-2006, 06:24 PM

Thanks for that!

I've designed the site so that most of the data is read once and held in in the ASP.NET application cache. The Access DB will just be used for logging transactions, the secure part of which are handled by a third party provider. If I get to a high transaction rate (I wish...) I'll be able to justify switching to SQL Server without any probs...

1) Great - I can get the DSN working locally so I'm sure it will be fine when I deploy

2) I've tried fiddling, but I can't figure out how to connect Access to a remote access DB

3) I've realised I already have a solution to this...

Thanks.

Ian

16-08-2006, 06:24 PM	#3 (permalink)
IanStevenson Registered User Join Date: Dec 2005 Posts: 7	Thanks for that! I've designed the site so that most of the data is read once and held in in the ASP.NET application cache. The Access DB will just be used for logging transactions, the secure part of which are handled by a third party provider. If I get to a high transaction rate (I wish...) I'll be able to justify switching to SQL Server without any probs... 1) Great - I can get the DSN working locally so I'm sure it will be fine when I deploy 2) I've tried fiddling, but I can't figure out how to connect Access to a remote access DB 3) I've realised I already have a solution to this... Thanks. Ian