I need the native resolution of the server, such as 1024x768 to be in each quadrant, just scaled down. There are quadscreen splitters that do this by accepting 4 DVI inputs and outputing one, but I'd rather use something in software on the virtual server if its available.
Thanks for the reply.
Actually, I need them to display simultaneously in 4 quads of the screen, but maintain the aspect ratio and have no scrolls.
Thanks for the reply though.
I'm looking at MS Virtual Server 2005 R2 to migrate my physical servers overs to. I need to display multiple Remote Desktop sessions on a single screen, but have them scale down so that there are no scroll bars. I want to then project that onto a screen. Any ideas on the scaling of the desktop?
Yes. OK, now that I understand you ... if I don't use lookups in the table, how can I create a dynamic form that decides when to use combo boxes? Is there a way to query the relationship model or do I hard code it in VBA or is dynamic forms out of reach?
Thank you for your help.
Thank you. I think that might do the trick. I did read, howeve, the Evils of Lookup fields and I'm confused. How do I create relationships in Access (relationships view) if I do this? Should I just control the relationships with VBA and keep Access in the dark?
I'm trying to create a dynamic form that is built based on a table that is given when the function is called.
The form has Textboxes labeled txtFieldy where y is 0 - 18. My lookup fields always have ID in them and is converted to a combobox. The first ID field is skipped.
My problem is...
Progran TOFT (Timed Overflow) and OVDN (Overflow DN). OVDN must be ACD Q, I think. You may get creative with MERMAIL or CALLPILOT and an Application to transfer out to Regular DN if you try hard enough. Use CALLPILOT ACD Q DN for OVDN and play with it.
Depending on what type of PRI you are using, the telco may not expect or allow certain digits. With an NI2 PRI and the DMS-100, translations are required for LD and INTL calls. The DMS will not expect 011 with INTL call, the TON will be sent as INTL and used.. Also digits 1+ may not be...
Goto LD 96
If you get DCH001, you do not have the ISDN package and cannot setup CLI yourself; the telco would do it.
Nortel recommends not doing this on a high traffic system.
In LD 96 Type
STAT DCH "look at what your DCH is"
ENL MSGO x "where x is your DCH - Turns on outgoing...
I keep seeing people mentioning not changing ACD phones. I should OUT and NEW if I would like to change .... Does this apply to ANY change or just a change to the ACD related keys or functions? Is it safe to change CLS other KEYs on that same phone?
I can get Local calls to go out on PRI, but no LD. I'm using a RLI that has DMI of 0. I turned on D-channel messaging and see that NPI is e164 and TON is LOCL for the NXX calls I make. The call goes through. I setup LD calls as SPN or NPA and cannot get them to go through unless I set CTYP to...
Well after getting LD calls to go over PRI and getting CNUM and CNAM coming in, I am having outbound CLID problems. When I dial to a residential analog line with Caller ID at the Telco, my number displays unknown. When I dial a cell number that is setup using the same RLI in NXXs, I have the...
A solution. In table LTCALLS in the DMS-100. Option BNS=SBN. Special Billing number is used from table TRKGRP. I'm not satisfied with how I understand the manipulation of NPA in AC1 and CTYP in DMI and how that sent different Type of Number and Number plan during the D-channel SETUP message...
My d-channel messaging says that I'm sending 1+NPA+NXX+XXXX like before NI2. The Telco did a DISPLAY CALL on the DMS and saw the digits mentioned. They add 10288+ .... like before. It seems to be something related to Billing DN which they still have setup or Numbering Plan or Type of Number...
I only have one PRI. Local and LD must both go across it. Using IFC d100, all were set to SPNs. Digits dialed were digits sent to the local telco. Now with IFC set to NI2, It appears that the Type of Number field and other programming is what might be incorrect. I now have D-channels set to...
1. Yes, it has been working using D100. The telco doesn't support NI2, but is willing to test it in this case. It is changed to NI2 when I test.
2. Haven't spoke to the LD carrier yet. Our BILLDN is setup of the trunk group at the telco and that is pic'd to our carrier. We just dial 1+...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.