Where are NetMailer JOBS stored

[RobertJWilkins]

Greetings

I am running A5V6 and Multi-User Netmailer.

There are several e-mail profiles and stored Jobs used by the people in our office.

When I move an A5 update from my development environment to my production environment (by copying certain data files with specific file extensions) I erase all of the existing netmailer Jobs in the production environment ?????

Where are the netmailer jobs stored
(what database file extension ??)
and is there a way that I can update the production environment without destroying all the existing profiles and jobs ...

Thanks in advance

Bob Wilkins
Ontario, Canada

[AaronBBrown]

Netmailer jobs are stored in the data dictionary for the table or set on which they are based. Email profiles are stored in the registry for the current user/version of Alpha Five running. If your Netmailer jobs disappeared, so too would your Forms/Reports/Layouts.

I'm not sure what you mean by "Multi-User Netmailer." There are only two version of Netmailer, Basic and Professional and they differ only by the inclusion of maintenance jobs.

[RobertJWilkins]

Hi Aaron

Thanks for your quick reply.

We are using the multi user net mailer runtime version.
Does that identify it for you - NOT the professional version.
Maybe the "multi user" is a misnomer - but it is being used in a 8 station peer-to-peer networked environment.

So.... if the netmailer jobs are stored in the data dictionary files for a table (or a set) and I make changes to a form based on that table (or set) then when I move the updated ddd, ddm and ddx (set, sem and sex) files to "Production", I loose the netmailer jobs --- any solution for not doing this ???

Each update about 5 people have to re-create 3 or 4 already existing netmailer jobs, and I am not very popular ??? THANKS again

Bob

[AaronBBrown]

The Netmailer jobs are stored in the ddd, ddm, ddx, set, sem, sex files. As I said, if you are not losing your forms, you should not be losing your Netmailer jobs.

So.... if the netmailer jobs are stored in the data dictionary files for a table (or a set) and I make changes to a form based on that table (or set) then when I move the updated ddd, ddm and ddx (set, sem and sex) files to "Production", I loose the netmailer jobs --- any solution for not doing this ???

[RobertJWilkins]

Hi AAron, lets try this again......

The staff net mailer jobs are NOT in my development ddd files. The staff make them up on the fly as needed.
(more are added weekly by various staff members)
The staff only have the run-time version of A5V6

I, as the developer of the system, make any necessary updates/changes to the forms in my development version of the system. Add new forms, change xbasic code as necessary etc. etc. etc.

When the development system works properly, I copy the associated files (listed above) over to the production version and VOILA !!! wipe out all their net-mailer jobs

And the staff yell and scream and throw things at me .......

Any suggestions ???
(nice ones!!!)

[Brad Chesnut]

When you do the developement, are you pulling the datafiles in use where the netmailer jobs are being created, or do you have a master set that you update and then OVERRIDE the files in use which would hold the Netmailer jobs created?

Just a thought.

[Al Buchholz]

A couple of ideas

Robert

There are a couple of ways to avoid the conflict that you are having. The problem is caused by there being more than one developer ( one is you, the other is the user(s) developing the netmailer objects.

It is workable and there are different options that depend on the exact circumstances and your preferences.

The solution is to working atomically on the objects instead of working with the structure files that contain multiple objects and over write other objects.

Here are some methods and utilities to help.

1. Use the Alpha copy to option to copy an object from one table to another table in the same database or to another table in another database.
2. Keep a development directory(db) on the clients site that is yours and move from there into the production directory(db). - using the method 1.
3. Use to your advantage that the copy to can copy an object from one table(/set) to another table(/set) even if the result results in errors if it's used. A second copy can move it to a table(/set) and it then has the proper basis and no errors....

4. Use Jim Chapman's routine to export objects to an .abn file that can be imported into another table(/set) in another database.
See this thread http://msgboard.alphasoftware.com/al...ad.php?t=22900
and the newsletter. The downside of Jim's routine is that operations are not an option. But scripts are... So if you really need to move from one db to another, either make the operation a script or use point 1-3 or point 5.

An interesting advantage of Jim's routine is that you have a .abn file that contains one object and you match documentation to it.

5. Look in the code archive for Finian's utility to copy objects similar to the steps in 1-3.

All of these steps have been used extensively and have performed without fail. They are a must for any multi-user development environment. Unless you don't value your sanity.....

[AaronBBrown]

Now that you've explained your situation, I understand what the problem is.

The netmailer jobs are stored in the data dictionary with a type of "BKEM" (bulk email). When I get to work I can send you some sample code on how to get the data from the Netmailer jobs.

[Davidk]

Re: Where are NetMailer JOBS stored

Hey Aaron,

Could you post this code for us, that you mention?

Thanks so much.

David

[MikeC]

Re: Where are NetMailer JOBS stored

David,
Aaron hasn't been around since about August of 2007 working for Alpha...he did drop by a while ago, but just to say "hi".

[Davidk]

Re: Where are NetMailer JOBS stored

Thanks Mike... I thought that last posting that you refer to meant he was still here.