Answer is indeed to delete the new & empty AVDATA database (or just don't create it during the initial installation of the SQL server.) Then restore the backup to AVDATA and it will create a new and populated database. I haven't fully tested the new one, but it looks OK so far.

FYI, I am still using SQL Server 2005 Express, and AirVision and the SQL server share the same PC. I migrated the setup from a Windows 7 PC to a Windows XP box.

There is a DUH! moment were Rena' pointed out that I probably had never clicked on the "overwrite exisiting database" option! Maybe none of this discussion would have been necessary if I had!

Ben

 out of  found this valuable. Do you find this valuable?    

Bob, Sorry to take so long to answer. Although I'm not intimately familiar with the combo BAMS, the feed for BP comes from the MetOne BP/AT BX-596 Ambient AT/BP Combo Sensor that is typically wired to Channles 6 and 7 on the back of the BAMs. This signal is typically not stored or logged by the BAM its simply used internally to adjust to the various sample condtions. To get external BP logged by the BAMs for collection I jumpered a wire from the sensor BP + input channel to the + side of one of the 6 programmable BAM logging channels on that BAM. Once you know the channel has the BP jumpered to it you simply have to indentify(count) that data point position in the data string output by the BAM and that is your Column # for your file import column mapping. Hope this helps I sent you a PM also.

 out of  found this valuable. Do you find this valuable?    

Absolutely. In the matrix data editor, you can select, drag-select, or shift/ctrl-select cells, and right-click for editing functions.

I will check into the refresh in the data editor. I had not noticed that (I know it will refresh after each 'save', but you don't have to hit save after each individual edit).

For zero values, you can use the filter fields in any of the data editors to filter the data set down to values < 0, and then you can batch-edit the filtered results (changing the value AND applying the qualifier code), making it quick and easy to handle zero data.

1  out of 1 found this valuable. Do you find this valuable? Do you?    

"After stopping SQL services, the Conversion software could be uninstalled and reinstalled from disc. The new install from 1.0.2 disc seems to be the same version as shown on this "Converting E-DAS Data" page."

The main distinguishing feature between the 1.0.1 and 1.0.2 conversion utility is that the 1.0.2 utility adds the ability to convert Sample data, if I recall correctly.

 out of  found this valuable. Do you find this valuable?    

"I left the computer running the conversion process, and returned to find there had been a power outage. How do I find out if the process completed before the power outage?"

We don't keep a log- if you remember the time period for which you converted data, you can just check that data range.

If you were converting configuration as well, check to see if you got the converted site names, channel names, etc- it does the configuration conversion LAST, so if you selected config conversion and you got it, chances are it finished.

 out of  found this valuable. Do you find this valuable?    

"Our system is insalled in a Server Downtown no modems allowed. I am setting up Executive on my old polling Central System . Keep getting refused connection to IP adress and port?"

I assume the downtown server is just for the SQL database? Keep in mind that there are three minimal components to the system- the SQL database (and related SQL server), the Executive (e.g., the PC running the AirVision service), and the Client application. They can all reside on one PC, two, or three separate PCs. The Executive (the PC running the AirVision service) would be the hardware point where any COM ports / modems would be referenced.

Usually, when you have this configuration and the Client can't log in and get that message, the problem is that the AirVIsion Service isn't running on the "Executive" PC at all. You can verify this by going to the Executive PC and selecting Manage->My Computer->Services (or typing Run->services.msc).

If the Service isn't running, there are two common reasons:
1. The local account (which is the default) on the Executive PC used to run the service (right click on the AirVision service, select Properties->LogOn) often doesn't have the rights in a domain environment to log into the SQL server. You may need to replace the default local system account with a domain admin account.
2. Server Settings editor hasn't been run on the Executive PC, or the SQL server instance is incorrectly entered. Make sure to use the exact name of the SQL instance.

If you've checked all of these and can't identify why the service isn't starting, grab your server log file (C:\Documents and Settings\All Users\Application Data\Agilaire\AirVision\Server\Log\AVServerExceptions.[date].txt) and email to Agilaire Support.

 out of  found this valuable. Do you find this valuable?