Good Morning Sage Community, My employer is a long time Timeslips user without much technical expertise. In the wake of a server crash (in which the C drive was not affected), we migrated all the data from the hard drive of the server to a non server machine. This 'server' is running Windows 7. My employer is complaining that not only is his OfficeManager.dsb file being located upon startup, but he is missing some of the typical Timeslips functionality. Slip entry is still possible. In a future edit, I will probably elaborate on some of this missing functionality. I have backed up our database, but I do not know how I should proceed in attempting to fix this problem. In addition to the aforementioned issue, there are also apparently paradox issues though these might be unrelated. It appears my options are the following: 1) Attempt to locate OfficeManager.dsb in workstations or local installs. (All attempts to find it in relevant timeslips directories have proved fruitless) 2) Attempt to freshen install path. Presumably in the migration of an installation to the surrogate 'server' computer, the Timeslips.cfg file was somehow adversely affected, though this is mere speculation. Both workstations are currently using the same cfg files. 3) Attempt complete reinstallation ( I don't want to lose billing templates, but I dont know how to back those up, or if my employer is using pre-packaged templates) How should I proceed? I don't believe the OfficeManager.dsb file is anywhere to be found. If i attempt complete reinstall on all three workstations (including our surrogate server), which should I make the administrator (is that even applicable?)? What should I backup before doing so? Do I install via CD to the server and then from the mapped network drive install to each workstation or install timeslips on all three with CDs and just point them all to the CFG file located on the surrogate server? Thank you for your time.
↧
