Contents. Physical and chemical properties In purer forms, crack rocks appear as off-white nuggets with jagged edges, with a slightly higher density than candle wax. Purer forms of crack resemble a hard brittle plastic, in crystalline form (snaps when broken). A crack rock acts as a (see: ), numbing the tongue or mouth only where directly placed.
Good Evening Everyone, My client needs to know if we can load the PowerBuilder 9.02 Development software on a Citrix Environment so that the Developers in India will be able to access the network DataBase (Oracle, Sybase, or MS SQL Server) and SourceSafe back in the USA?
Purer forms of crack will sink in water or melt at the edges when near a flame (crack vaporizes at 90 °C, 194 °F). Crack cocaine as sold on the streets may be or 'cut' with other substances mimicking the appearance of crack cocaine to increase bulk. Use of toxic adulterants such as has been documented. A close up of the 'cooking' process that creates crack. (NaHCO 3, common baking soda) is a base used in preparation of crack, although other may substitute for it. The net reaction when using sodium bicarbonate is Coc-H +Cl − + NaHCO 3 → Coc + H 2O + CO 2 + NaCl With: Coc-H +Cl − + NH 4HCO 3 → Coc + + CO 2 + H 2O With: 2(Coc-H +Cl −) + (NH 4) 2CO 3 → 2 Coc + 2 NH 4Cl + CO 2 + H 2O Crack cocaine is frequently purchased already in rock form, although it is not uncommon for some users to 'wash up' or 'cook' powder cocaine into crack themselves. This process is frequently done with baking soda (sodium bicarbonate), water, and a spoon.
Once mixed and heated, the bicarbonate reacts with the hydrochloride of the powder cocaine, forming free base cocaine and (H 2CO 3) in a reversible acid-base reaction. The heating accelerates the degradation of carbonic acid into (CO 2) and water. Loss of CO 2 prevents the reaction from reversing back to cocaine hydrochloride. Free base cocaine separates as an oily layer, floating on the top of the now leftover aqueous phase. It is at this point that the oil is picked up rapidly, usually with a pin or long thin object. This pulls the oil up and spins it, allowing air to set and dry the oil, and allows the maker to roll the oil into the rock-like shape.
Crack vaporizes near temperature 90 °C (194 °F), much lower than the cocaine hydrochloride melting point of 190 °C (374 °F). Whereas cocaine hydrochloride cannot be smoked (burns with no effect), crack cocaine when smoked allows for quick absorption into the blood stream, and reaches the brain in 8 seconds. Crack cocaine can also be injected intravenously with the same effect as powder cocaine. However, whereas powder cocaine dissolves in water, crack must be dissolved in an acidic solution such as lemon juice or white vinegar, a process that effectively reverses the original conversion of powder cocaine to crack. Recreational use.
A woman smoking crack cocaine. Crack cocaine is commonly used as a recreational drug. Effects of crack cocaine include, supreme confidence, loss of appetite, alertness, increased energy, a craving for more cocaine, and potential paranoia (ending after use). Its initial effect is to release a large amount of, a brain chemical inducing feelings of. The high usually lasts from 5–10 minutes, after which time dopamine levels in the brain plummet, leaving the user feeling and low. When (powder) cocaine is dissolved and, the absorption into the bloodstream is at least as rapid as the absorption of the drug which occurs when crack cocaine is smoked, and similar may be experienced.
Main physiological effects of crack cocaine The short-term physiological effects of cocaine include constricted blood vessels, and increased temperature, heart rate, and blood pressure. Some users of cocaine report feelings of restlessness, irritability, and anxiety. In rare instances, sudden death can occur on the first use of cocaine or unexpectedly thereafter. Cocaine-related deaths are often a result of or seizures followed by respiratory arrest. Like other forms of cocaine, smoking crack can increase heart rate and blood pressure, leading to long-term cardiovascular problems. Some research suggests that smoking crack or freebase cocaine has additional health risks compared to other methods of taking cocaine.
Many of these issues relate specifically to the release of and its effect on the heart, lungs, and liver. Toxic: Many substances may have been added in order to expand the weight and volume of a batch, while still appearing to be pure crack. Occasionally, highly toxic substances are used, with a range of corresponding short and long-term health risks. Adulturants used with crack and cocaine include, sugars such as,. Smoking problems: Any poses its own set of health risks; in the case of crack cocaine, smoking tends to be more harmful than other routes.
Crack users tend to smoke the drug because that has a higher than other routes typically used for drugs of abuse such as. Crack has a melting point of around 90 °C (194 °F), and the smoke does not remain potent for long. Therefore, crack pipes are generally very short, to minimize the time between evaporating and ingestion (thereby minimizing loss of potency). Having a very hot pipe pressed against the lips often causes cracked and blistered lips, colloquially known as 'crack lip'.
The use of 'convenience store crack pipes' – glass tubes which originally contained small – may contribute to this condition. These 4-inch (10-cm) pipes are not durable and will quickly develop breaks; users may continue to use the pipe even though it has been broken to a shorter length. The hot pipe might burn the lips, tongue, or fingers, especially when passed between people who take hits in rapid succession, causing the short pipe to reach higher temperatures than if used by one person alone. Pure or large doses: Because the quality of crack can vary greatly, some people might smoke larger amounts of diluted crack, unaware that a similar amount of a new batch of purer crack could cause an overdose. This can trigger heart problems or cause unconsciousness. Pathogens on pipes: When pipes are shared, bacteria or viruses can be transferred from person to person. Crack lung In crack users, acute respiratory symptoms have been reported, sometimes termed crack lung.
Symptoms include fever, hemoptysis and difficulty breathing. In the 48-hour period after use, people with these symptoms have also had associated radiographic findings on chest xray of, and infiltration. Psychological Stimulant drug abuse (particularly and cocaine) can lead to (aka Ekbom's Syndrome: a mistaken belief they are infested with parasites). For example, excessive cocaine use can lead to, nicknamed 'cocaine bugs' or 'coke bugs', where the affected people believe they have, or feel, parasites crawling under their skin. (Similar delusions may also be associated with high fever or in connection with alcohol withdrawal, sometimes accompanied by visual hallucinations of insects.) People experiencing these hallucinations might scratch themselves to the extent of serious skin damage and bleeding, especially when they are delirious. Paranoia and anxiety are among the most common psychological symptoms of crack cocaine use.
Psychosis is more closely associated with smoking crack cocaine than intranasal and intravenous use. Pregnancy and nursing. Main article: 'Crack baby' is a term for a child born to a mother who used crack cocaine during her pregnancy. The threat that cocaine use during poses to the is now considered exaggerated. Studies show that prenatal cocaine exposure (independent of other effects such as, for example, alcohol, tobacco, or physical environment) has no appreciable effect on childhood growth and development.
However, the official opinion of the of the United States warns about health risks while cautioning against stereotyping: Many recall that 'crack babies', or babies born to mothers who used crack cocaine while pregnant, were at one time written off by many as a lost generation. They were predicted to suffer from severe, irreversible damage, including reduced intelligence and social skills. It was later found that this was a gross exaggeration. However, the fact that most of these children appear normal should not be over-interpreted as indicating that there is no cause for concern. Using sophisticated technologies, scientists are now finding that exposure to cocaine during fetal development may lead to subtle, yet significant, later deficits in some children, including deficits in some aspects of cognitive performance, information-processing, and attention to tasks—abilities that are important for success in school.
There are also warnings about the threat of: 'It is likely that cocaine will reach the baby through breast milk.' The advises the following regarding cocaine use during pregnancy: Cocaine use during pregnancy can affect a pregnant woman and her unborn baby in many ways. During the early months of pregnancy, it may increase the risk of miscarriage. Later in pregnancy, it can trigger preterm labor (labor that occurs before 37 weeks of pregnancy) or cause the baby to grow poorly.
As a result, cocaine-exposed babies are more likely than unexposed babies to be born with low birthweight (less than 5.5 lb or 2.5 kg). Low-birthweight babies are 20 times more likely to die in their first month of life than normal-weight babies, and face an increased risk of lifelong disabilities such as mental retardation and cerebral palsy. Cocaine-exposed babies also tend to have smaller heads, which generally reflect smaller brains. Some studies suggest that cocaine-exposed babies are at increased risk of birth defects, including urinary-tract defects and, possibly, heart defects. Cocaine also may cause an unborn baby to have a stroke, irreversible brain damage, or a heart attack. Reinforcement disorders Tolerance An appreciable tolerance to cocaine's high may develop, with many addicts reporting that they seek but fail to achieve as much pleasure as they did from their first experience. Some users will frequently increase their doses to intensify and prolong the euphoric effects.
While tolerance to the high can occur, users might also become more sensitive to cocaine's local anesthetic (pain killing) and convulsant (seizure inducing) effects, without increasing the dose taken; this increased sensitivity may explain some deaths occurring after apparent low doses of cocaine. Main article: Crack cocaine is popularly thought to be the most addictive form of cocaine. However, this claim has been contested: Morgan and Zimmer wrote that available data indicated that '.smoking cocaine by itself does not increase markedly the likelihood of dependence. The claim that cocaine is much more addictive when smoked must be reexamined.'
They argued that cocaine users who are already prone to abuse are most likely to 'move toward a more efficient mode of ingestion' (that is, smoking). The intense desire to recapture the initial high is what is so addictive for many users. On the other hand, Reinarman et al.
Wrote that the nature of crack addiction depends on the social context in which it is used and the psychological characteristics of users, pointing out that many heavy crack users can go for days or weeks without using the drugs. Overdose A typical response among users is to have another hit of the drug; however, the levels of in the brain take a long time to replenish themselves, and each hit taken in rapid succession leads to progressively less intense highs. However, a person might binge for 3 or more days without sleep, while inhaling hits from the pipe.
Use of cocaine in a binge, during which the drug is taken repeatedly and at increasingly high doses, leads to a state of increasing irritability, restlessness,. This may result in a full-blown paranoid psychosis, in which the individual loses touch with reality and experiences auditory hallucinations. Large amounts of crack cocaine (several hundred milligrams or more) intensify the user's high, but may also lead to bizarre, erratic, and violent behavior. Large amounts can induce tremors, muscle twitches, or, with repeated doses, a toxic reaction closely resembling poisoning. Anti-crack poster Cocaine is listed as a drug in the United Nations 1961, making it illegal for non-state-sanctioned production, manufacture, export, import, distribution, trade, use and possession.
In most states (except in the U.S.) crack falls under the same category as. Australia In Australia, crack falls under the same category as cocaine, which is listed as a, indicating that any substances and preparations for therapeutic use under this category have high potential for abuse and addiction. It is permitted for some medical use, but is otherwise outlawed. Canada As a under the, crack is not differentiated from cocaine and other products. However, the court may weigh the socio-economic factors of crack usage in sentencing. As a guideline, Schedule I drugs carry a maximum 7-year prison sentence for possession for an and up to life imprisonment for trafficking and production.
A on possession carries a $1000–$2000 fine and/or 6 months to a year imprisonment. United States In the United States, cocaine is a drug under the, indicating that it has a high abuse potential but also carries a medicinal purpose.
Under the Controlled Substances Act, crack and cocaine are considered the same drug. The increased penalties for crack cocaine possession and usage. It mandated a of five years without for possession of five grams of crack; to receive the same sentence with powder cocaine one had to have 500 grams. This sentencing disparity was reduced from 100-to-1 to 18-to-1 by the of 2010. Europe In the United Kingdom, crack is a under the.
In the it is a List 1 drug of the.
Delivering the Completed Application to End Users Once the PowerBuilder target application has been compiled into an executable version, it must be packaged and delivered to the desktops of the end users. This is not as simple as copying the EXE and PBD files onto the user's computer. Several commercially available software installation packages are available today.
Tools like this are responsible for collecting all the components of the software distribution and 'packaging' them into a single installable unit. Some of the more popular tools for this are. InstallShield (. Wise Installer. InstallAnywhere. Windows Installer There are several additional components to a successful end-user deployment of the application.
The following installation checklist covers both the application-specific items as well as the environmental items. Environmental Components The items listed in this section are concerned with the runtime execution environment, also known as the 'Virtual Machine.' These consist of the PowerBuilder Runtime DLLs, Database Interface DLLs, and any other supporting software, outside of the PowerBuilder application code. PowerBuilder Runtime DLLs The runtime DLLs enable PowerBuilder applications to run outside of the IDE, and they are required whether or not the application was compiled to machine code DLLs or Pcode PBDs. For optimal performance, these files should be installed locally on each end user's machine. They can be found on development workstations in the folder C: Program Files Sybase Shared PowerBuilder. These files are shown in Table 3.5.
Table 3.5 PowerBuilder Runtime Files for Deployment PBVM90.DLL Required for all applications LIBJCC.DLL Required for all applications PBDWE90.DLL Datawindow/Datastore engine PBRTC90.DLL Rich Text PBFNT90.INI Maps unavailable fonts PBLAB90.INI Label datawindow style predefined formats PBTRA90.DLL Database connection tracing PBFNT90.INI Font substitution mapping file It's only required to deploy the files supporting features that are implemented by your application. For example, if your application does not use Rich Text, PBRTC90.DLL is not required. It is also important that the same versions of these files are used to develop, compile, and run the applications. When deploying them to the end-user machine, they can be placed in one of three locations:. In the same folder as the executable. In a folder that has been added to the system PATH variable. In a folder that has been added to the application's AppPath registry key.
This key is HKEYLOCALMACHINE Software Microsoft Current Version AppPaths Localized runtime files are provided for French, German, Italian, Spanish, Dutch, Danish, Norwegian, and Swedish. These files are usually available shortly after the general release of a new version of PowerBuilder.
The localized runtime files let you deploy PowerBuilder applications with standard runtime dialog boxes in the local language. They handle language-specific data when the application runs. However, this does not imply that an application can be translated into a specific language simply by deploying the localized runtime files. Significant consideration must be given to many design issues when developing an application for multi-language support.
Sybase has several White Papers available on this topic at. Database Interface Files If the PowerBuilder application accesses a datasource, whether the datasource is a relational database or not, you must also deploy the specific drivers for that datasource. These can be either the 'native' drivers, or 'generic' ODBC, JDBC, or OLE DB drivers. The list of database drivers shown in Table 3.6 are provided with the Professional and Enterprise versions of PowerBuilder 9. Table 3.6 PowerBuilder Native Database Interface Runtime Files for Deployment PBIN790.DLL Informix I-Net 7 PBIN990.DLL Informix I-Net 9 PBMSS90.DLL Microsoft SQLServer 6 and 7 PBO7390.DLL Oracle 7.3 PBO8490.DLL Oracle 8.0.x and Oracle 8i 8.1.x PBO9090.DLL Oracle 9.x PBDIR90.DLL Sybase DirectConnect PBSYC90.DLL Sybase Adaptive Server Enterprise CT-LIB PBSYJ90.DLL Sybase ASE CT-LIB (for EAServer deployment only) ODBC Drivers and Profiles Microsoft's Open Database Connectivity (ODBC) standard provides an alternative method of connecting to ODBC-compliant datasources. Table 3.7 lists the files that are required for data connections from PowerBuilder to ODBC datasources.
Table 3.7 PowerBuilder ODBC Database Interface Runtime Files for Deployment PBODB90.DLL Generic ODBC Driver PBODB90.INI -Initialization file for ODBC access (required for ODBC applications) Accessing a database through an ODBC driver also requires an ODBC Profile. These are Registry settings or.DSN files that encapsulate the driver configuration that is pertinent for the selected database.
For more information on ODBC profiles, refer to Chapter 12, 'ODBC.' Installing these profiles on the client machine can be accomplished by including the appropriate registry settings in the deployment package. OLEDB Drivers and Profiles OLE DB is a standard Application Programming Interface (API) developed by Microsoft. It is a component of Microsoft's Data Access Components software, and OLE DB version 2 is required. OLE DB, much like ODBC, provides a standard interface to a number of different data sources.
NOTE The PowerBuilder Professional and Desktop versions do not support the OLE DB interface. PBOLE90.DLL is the PowerBuilder OLE DB database driver file that must be deployed to support OLE DB connections. JDBC Drivers and Profiles PowerBuilder 8 introduced the Java Database Connectivity (JDBC) interface, and support for this driver continues in PowerBuilder 9. The JDBC interface in PowerBuilder 8 supports both the Microsoft Virtual Machine (VM) and the Sun Java Runtime Environment (JRE) versions 1.1 and later. The JDBC interface in PowerBuilder 9 supports the SunJRE version 1.2 and later. If your application uses JDBC connections, the JDB driver will be required, as well as the appropriate Java package for the Java VM that is being used.
A vendor-supplied JDBC-compliant driver, such as Sybase Jconnect, will also need to be installed and configured on the machine making the database connection. Use the JavaVM DBParm parameter to specify which Java VM to use for the JDBC connection.
Table 3.9 lists the deployment requirements for applications using the JDB database interface. Table 3.9 PowerBuilder JDBC Database Interface Runtime Files for Deployment PBJDB90.DLL PowerBuilder JDBC DB Driver (JDB) for the Sun JRE 1.2 or later pbjdbc1290.jar Java package for PowerBuilder JDB driver and JRE 1.2 or later PowerBuilder Runtime Packager The preceding sections have presented the lists of PowerBuilder runtime files that must be deployed with the compiled executables. The good news is that a new utility called the PowerBuilder Runtime Packager, released with PowerBuilder 9, makes this list completely obsolete! The Runtime Packager, PBPack90.exe, can be found in the Program Files Sybase Shared PowerBuilder folder.
It takes the guesswork out of runtime file deployment by creating a Microsoft Installer package that contains exactly the files that your application will require. Shows the Runtime Packager window, which consists of three main sections:.
PowerBuilder Base Components: This section has no selectable options because it represents the files that must be deployed for any PowerBuilder application. Database Interfaces: In this section, select the database interface(s) that the application will require. The Packager will automatically select and include only those DLL files that implement the chosen interfaces. Other Components: This section lists four optional components available to PowerBuilder 9 applications. If the deployed application takes advantage of any of these four new capabilities in version 9, select the option to add their respective files to the runtime deployment kit. These four areas are XML Support, PB DOM (Document Object Model), EJB client, or SOAP Web Service client.
PowerBuilder Runtime Packager. At the bottom of the window is a field to enter the name of the Microsoft Installer (.msi) package that will be created. The.msi package that is created can be packaged along with the EXE and PBD/DLLs of the compiled PowerBuilder application, and deployed to the client machines as a single, seamless install kit. Database Client-side Communication Software Many database vendors include a client-side communication component, such as Oracle's SQLNet, or Sybase's CT-Lib. If your application is to successfully connect to the back-end database, you will need to also include this component in the installation package.
Application Components This section covers the deployment requirements for the actual compiled application code itself. These are the components that will execute in the runtime environment that was discussed in the previous section. The Executable Application This component will consist of the EXE file, any dynamic libraries (the Pcode PBDs or machine code DLLs), and any external resource files that are being delivered separately (BMPs, ICOs, and so on). For optimal performance, these files should be installed locally to each machine that will run the application. It is possible to install these files to a shared LAN folder, but that architecture is not recommended for performance reasons. If these files will be updated with maintenance releases, an effective architecture for managing the distribution of these files to the end-user machines is critical.
One possible approach is to place the revised files into a designated location on the LAN, and then have the application itself detect the presence of new versions of these files upon startup. The application can then copy the new files from the LAN location into the appropriate folder on the local machine and restart.
Any Additional Supporting Files This can include application-specific INI files, Help files, or additional documentation, such as User Guides. In some situations, it might be more appropriate to install these resources onto a shared LAN folder, rather than on each individual workstation.
Local Database Files If the application is going to be using a local database instead of accessing a server database across the network, it will be necessary to package up the database files for installation on the local machine. C/C Runtime Files for PBNI Components The PowerBuilder Native Interface (PBNI) is a new feature of PowerBuilder 9, and it enables developers to extend the functionality of PowerBuilder with modules written in C or C. The most frequently used type of PowerBuilder extension is to 'wrap' a C or C DLL, and expose its methods as PowerBuilder NVO functions. The PBNI utility PBX2PBD90.EXE produces a PowerBuilder PBD file that contains the interfaces for the C/C components. For a detailed explanation on the use of the PBNI facility, refer to Chapter 19, 'PowerBuilder Native Interface.'
Because PBNI components are actually written in C or C, it will be necessary to deploy the corresponding C or C runtime DLLs along with the compiled.PBD files. Refer to the documentation for your C/C compiler for the list of required runtime files. External Program Files This can include supporting software that is embedded in the application, such as OLE or OCX controls. Your install package might need to install these components and also register them to the Windows registry. You might not be legally allowed to redistribute external third-party software such as Microsoft Office or an email application.
In that case, simply have your application check to see if the required software is already installed and properly licensed.