Jump to content

jlze

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jlze

  • Rank
    newbie
  1. The OS is the same. It is a calculation field (Total Paid) based on summing the amount in the related table ledger. Once the find is broken it remains broken for the user.
  2. Occasionally, we have a problem where the user will perform a daily routine find and it will return no records found in FMP 8.5 when it should return a count. Also, when I do the same find in FMP Advanced 8.5 it will return a found count. Not sure what is happening but I would like to know if anyone has any ideas.
  3. jlze

    Set Layout Order

    Very interesting. I pretty sure it is not the latter because we never use the layout number for navigation purpose, strictly the name. Were there other issues you encountered with the mix of 7 & 8 clients and Server 7?
  4. jlze

    Migration

    We have been running FMS 7 and FMP 7 & 8 clients for awhile now. We are looking to move clients and servers to 8 but wanted to know if anyone has had any issues, especially with ODBC and/or file corruption.
  5. jlze

    Set Layout Order

    Recently we deleted a few layouts and reorder the layouts in the same file. We found that that particular database starting to have navigation issues with our users. They would click a button to navigate to a specific layout and it would take them to the very first layout in the list. Has anyone experienced this?
  6. jlze

    can't see ODBC driver

    I was having the same issue and I found this article that is listed below on the datadirect website. Deleted the defaults and deleted drivers not needed and it worked. = After installing the Connect for ODBC drivers on a Windows platform, no listing appears for any of the drivers under the Drivers tab of the Microsoft ODBC Data Source Administrator. A quick check of the registry listing at HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INI and HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INIODBC Drivers shows appropriate registry key entries for drivers which would indicate that the drivers were successfully installed. Successive attempts to install/reinstall the drivers do not resolve the issue. In the windows registry editor tool ( regedit.exe ), open the registry key HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INIODBC Drivers Look for an entry in this key whose name is (Default) The value of this entry should be (value not set) When experiencing the problem described above, the value is actually set to an empty string.
×

Important Information

By using this site, you agree to our Terms of Use.