dbcreate system tray icon

[#1]

Folks,

Just wondering if there is a way to prevent the sqlanywhere icon from appearing in the taskbar on windows when using the dbcreate capi function?

For bonus points (:P). Is there a way to specify the ENG parameter for the dbcreate call to specify a unique dbeng12 instance for the database creation. We have a bunch of unit tests that create databases and when there are multiple builds running the database creations get tangled up and fail. We have a workaround for this issue so it isn't critical, just annoying...

Cheers, Dan

[VolkerBarth]

I assume you are refering to the DBCreate DBTools function.

From the docs, I would think that the startline parameter of the a_create_db should help, as you can specify the according database engine parameters here. And you can use the -n database server switch to name the database engine and the -qi switch (and possibly other -qX variants) to suppress the icon in the system tray.

So I would suggest (but have not tested) to use the startline to something like

a_create_db.startline = "dbeng12 -gp page_size -c 10M -n MyEngineXy -qi"

[Former Member]

We tried that Volker, it doesn't seem to suppress the icon, nor give the engine a specific name. Hence the bafflement.

We'll try what John has posted above.

Cheers, Dan

[VolkerBarth]

@Dan: Thanks for the clarification!

@John: Am I reading the docs on a_create_db wrong? Or is this a topic that might be clarified in the docs (Confine my comment to your answer)?

[johnsmirnios]

As I read the docs, they are not "incorrect". We do use the provided start line; the docs just neglect to say that we use ENG=dbinit_engine as well. The docs could be improved.

[VolkerBarth]

Yes, I agree on both points, given your profound explanation above (thanks!). So specifying "-n" is pointless.

Based on that, and back to the original question:

Shouldn't then specifying -qi (or any other of the -qX server options) have the desired effect?

[johnsmirnios]

The -q options should work but it won't solve the problem of running multiple concurrent dbinit invocations. I was going for the bonus points! 🙂