![]() ![]() If this extended privilege is not enabled, xDBC access to the file will not be possible, regardless of any other configuration that has been performed. You must enable the fmxdbc privilege in at least one privilege set to grant ODBC/JDBC access to a database. Figure 20.13 shows the extended privilege in question.įigure 20.13. As with other external access methods, it may make sense to create a special user for xDBC access, and limit xDBC to that user alone. Any privilege set that has the Access via ODBC/JDBC extended privilege enabled will permit all accounts using that privilege set to access the file via xDBC. Like other means of external access, such as access via FileMaker Mobile, or access via XML, access via xDBC requires that a specific extended privilege be enabled in each file to be accessed. Getting Your Databases Ready for ODBC/JDBC Access First, though, well look at how to configure individual databases to permit xDBC access by either means. Well first look at configuring the FileMaker Pro client for local ODBC access, and then consider how to configure FileMaker Server Advanced for remote ODBC access. In the second place, its necessary to configure the client application environment correctly, which generally means installing and configuring a driver of some sort. In the first place, its necessary to configure the data source to accept xDBC connections. Regardless of which specific means of access you use, a number of things are constant during setup of an xDBC connection. The FileMaker client can accept xDBC connections only from client applications running locally (on the same computer).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |