Great Plains Dexterity Dynamics eEnterprise Microsoft CRM Microsoft RMS Crystal Reports SQL International

Alba Home

Phones

Toll Free: 1-866-528-0577

Office: 1-630-961-5918

Cell (consultant-on-duty): 1-630-854-0597

Email: welcome@albaspectrum.com.

Alba Spectrum Technologies

Fragments of Popular Great Plains forums (our thanks to original posters)

Create an ODBC connection to Great Plains

Overview:
When using an ODBC data source on more than one PC, the data source name has to be the identical same name, such as “GPData” or some other meaningful easy to remember name.
Create the same named ODBC connection on every PC that needs to use the Access database.

1. Create a New ODBC connection and click the Machine Data Source TAB.
2. Choose SQL Server as the data source.  It’s near the bottom of the list.
  Note: This name is what is chosen in the Access database when you link table later on in this example.   Also this name is used on every PC (So make a note of it) If every PC in the building has the same name data source then any PC can open the Access database with out any modifications.

3. Choose the Server from the drop down box.  Click the Next button

4. Choose the Login method as shown below.  The default is NT Authentication.

Note: If you don’t get the login information correct it will not let you go past this point.
Also Note: If you are connecting to SQL Server database on the Internet the Server name will be an IP address 209.168.34.78 Or the WEB host will give you the name of the Server such as     clh.ij.net

5. Click the Next button at the bottom.

Once you get to this screen you have successfully logged in to the SQL server database.  Its down hill from here.
Put a Check in the Change to default database to: box and click the drop down to find the Database name where your data resides.
This is important because if you choose the wrong database you will be forever trying to find the information needed in Access later.
For Great Plains Dynamics it’s not the “Dynamics” database.  Instead choose the name of your company from this list.  Look up and down the list.

6. Choose the Language or leave it default.
Click the Finish button.
7. Click the TEST data source button to make sure it works OK.

Note: This procedure is done on Every PC that needs to connect to the Access database.

See the Next FAQ for Access to connect to this ODBC.

Connect Access to an ODBC datasource

On the PC at that needs Access to connect to Great Plains

1. Create the ODBC connection to the Real Company like so.
2. Open the Access database and close any forms that open automatically.
3. Click the Tables TAB.
4.Right click in the white space, then click Link Tables…
In the “Files of type” drop down (at the bottom) choose ODBC (at the bottom of this list)

The Same data source screen will pop up as above when you created the data source. Choose the name you gave it in the other FAQ.

5. Click the OK button.
This will bring up a list of all the tables in that SQL Server database.
First click the “Save Password check box (lower left) or it will ask you to login in everytime you open Access)

6. single click each table you want to use in the Access database.
7. Click OK when you are finished.

8. Next choose the Key Column(s).
Then click OK.
Note this box will pop up for each table you choose. So repeat the process.

9. Finally you will see the SQL Server tables linked (little black arrow on the left) with a Globe next to that. Also the table names will be dbo_xxxx.
10. If you want to rename the table do it now.

That's it

Use of an Index File

When using Source Code Control, all resources are stored in a text representation in your repository. They are stored with their names as the unique identifier.

In your development dictionary, the unique identifier is actually the internal Resource ID generated by Dexterity.  For third party developers (ie. most Dex Developers), these start at 22,000.

As you add resources (Forms, Tables, Reports, Field etc.), they are provided Resource IDs by whatever is next available.  So they end up being numbered in order they were created.

When creating a new build, you would start with a base DYNAMICS.DIC and then update all your resources from the repository.  During this process, resources are brought in in alphabetical order and are assigned Resource IDs as the resources are added. So now the Resource IDs are number in alphabetical order.  This is going to cause problems with updating of modified forms and reports, security records for access denied or alternate windows and generally make life very difficult.

The solution is the Index File, which tracks the Resource IDs assigned to resources and ensures that they are maintained between builds.

So to use the index file....

Make sure that the Edit >> Options >> Source Control >> Enable Administrative Features is checked for the developer in charge of the build process.

Every time a build is completed, select Explorer >> Source Control >> Update Index File from the menus.

Every time a create a new build, select Explorer >> Source Control >> Update. On the Update from Repository window select the Use Index File option. In the words of Dexterity Product Manager, "Just because it is an option does not mean it is optional".

This will ensure that resource ID's stay consistant between builds and between version releases.

How to use Named Printers with Terminal Server or Citrix?

thanks to David Musgrave

What is the best method of setting up Named Printers on a Terminal Server?

Things to note:

1) Named Printers is machine based.  It stores a Machine ID in the DEX.INI for each workstation and all settings are for the current workstation only.  In a Terminal Server environment it means that all users share the same settings because the are all using the same workstation.

2) It is not recommended to use Wokstation Printers with Named Printers as they can change depending on which machine is used to login to a terminal server session.  It is best to only select printers which are permanently visible to the terminal server.

3) Printers can be set up on a user basis which allows different users to have different configurations on the single workstation.

4) If using multiple application folders on the one terminal server or multiple terminal servers, please ensure that each has its own Machine ID.  You might need to manually edit the ST_MachineID setting in the DEX.INI.  You would then need to configure Named Printers on each each instance individually.

Situation 1: Single Location Access to Server
For a simple site where all users have their printers defined the same, just set up Named Printers as though it is a single workstation, using System or Company class printers.

Situation 2: Multiple Location Access to Server
For the more complex site where there are a number of remote locations accessing the server, you should use User class printers so that each user can have their own configuration defined.  However, when you use a user class printer you will find that is MUST be defined for all users and that can be time consuming.  Usually, all of the users from a single remote location will want the same configuration.  Named Printers has a way of setting this up simply and quickly.

The feature you need to use is Named Printers' Template Users, below is an example with the steps to set this up:

I have 3 remote locations using my terminal Server in Sydney. There are based in London, Paris and Fargo.  Each remote location has 30 users.

1) Create a New User ID for each remote location, and assign them access to the lesson company or a test company.  These User ID's will not be used to login.

2) Select Setup >> System >> Named Printers.  If this is first time you have used Named Printers, you will be asked to set up the Machine ID (normally the Computer's Network Name as this is unique). You would also need to set up the Default Printer ID, this should point to a printer based in Sydney.  The Default Printer ID is automatically assigned to the System Default Printer Task.

3) From the Assign Named Printers window, click on the Setup Button and then on the Advanced Button.  Using the bottom half of the window enter in the Template User ID as the remote location User ID and using the checkboxes, assign to it all the users from that location.  Repeat for each remote location.  You now have created your 3 Template Users.

4) From the Setup Named Printers window create all the Printer ID's needed for each location as User Class Printers assigned to the Template User for that location.  Repeat for each remote location.

5) Then from the  Assign Named Printers window, change the User and Company to one of the Template Users and the assigned company.  Set the Company Default Printer to Printer Class: User and select the default Printer ID to be used for that location.

6) Assign other user class printers to other Printer Tasks as required.  Repeat 5 and 6 for each location.

In this example, it was possible to complete the Named Printers setup by configuring 3 template users instead of the 90 individual users.