Results 1 to 4 of 4

Thread: Error Checking for Recordset [resolved]

Threaded View

  1. Sep 22nd, 2005, 11:40 AM #1
    just_a_me
    just_a_me is offline

    Thread Starter
    Addicted Member
    Join Date
    May 2005
    Posts
    230

    Error Checking for Recordset [resolved]

    I am writing a program that needs to run 24/7 for a couple weeks at a time. It writes a record with 14 fields to a single table database every 2 minutes or so. Would it be more appropriate for me to close and open the connection each time or leave the connection open all the time? I was thinking I should open and close it so that if I the network goes down I can write a csv to the harddrive until the network comes back up. Otherwise, there isn't a way to know if I've lost the connection is there?
    Last edited by just_a_me; Sep 22nd, 2005 at 02:08 PM. Reason: resolved
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules


Click Here to Expand Forum to Full Width