On 2017-03-17 20:16, Clyde Eisenbeis wrote: > I clearly misunderstood. > > To be certain I understand the terminology, an embedded server is one > that is accessible via the Internet?
No, Firebird Embedded is a (native) client API that directly accesses a Firebird database engine in the same process, it does not open ports that make the database server externally accessible. As a simplification, a normal Firebird server is a component that listens on the network (eg through TCP/IP) and accesses the database engine. When an application access this server through the native client API, this API translates the calls to the (TCP/IP) wire protocol, and the server-side translates this back to native calls that go to the database engine. On the other hand in Firebird embedded, the network part is skipped, so the native client access goes directly to the database engine. > I do want this database to eventually be accessible via the Internet. A Firebird Embedded is not network accessible. > I know which tables I want ... and which fields I want in each table. > > By dependencies, does that mean table names, field names, passwords, > sizes? No, by dependencies I mean other files (dlls) that are necessary for the Firebird database engine to run inside your C# process. > How do I create, or download, the Firebird embedded server? > > How do I create this database? As I said on stack overflow, I'll try to post a more complete answer later this weekend. Also check the other answer posted recently, the links in that mail handle some older versions, but should still apply in general. Mark ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
