> A biz friend has coded up his timesheet application in MS Access 2007,
> with the actual tables/files located on his remote hosted dedicated
> server running Sharepoint 2007.
>
> Everything has been running fine for months - until this week -
> Now, the application gets random errors on the tables,
> indicating an I/O error ?? different tables, different times, etc
>
> He can go onto Sharepoint and open the table & all is fine.
> But - back in Access - the table icon indicates the "link" is bad,
> and the only way he has found to "fix it" is to delete the link &
> re-establish it.
>
> Any ideas for him to chase down..... or how to handle these "error
> conditions"
> so that the link is not permanently broken ??
>
> thanks for any suggestions -
> --
> ----------------------------------
> "If everything seems to be going well,
> you have obviously overlooked something." - Steven Wright