What test reporting software are you using?

[SecondGen]

We are still on PowerDB 10 and it’s a nightmare, constant problems with getting job history and synchronizing our data. It could be the way we are using it, I’ve tried the new version a few times with rental equipment and it seems OK but our company wont upgrade.

Just curious as to what other guys are using and why you like/dislike it, I’m ready to go back to Word Documents and Excel Sheets.

[phasor]

We are still on PowerDB 10 and it’s a nightmare, constant problems with getting job history and synchronizing our data. It could be the way we are using it, I’ve tried the new version a few times with rental equipment and it seems OK but our company wont upgrade.

Just curious as to what other guys are using and why you like/dislike it, I’m ready to go back to Word Documents and Excel Sheets.

PowerDB 11 Pro here and honestly I can't really complain about it at all.

[SecondGen]

PowerDB 11 Pro here and honestly I can't really complain about it at all.

What kind of setup are you guys using, stock forms or custom? Do you host your own master DB?

[phasor]

What kind of setup are you guys using, stock forms or custom? Do you host your own master DB?

They are custom forms we have a person at our company who takes care of all PowerDB issues for us.

[SecondGen]

They are custom forms we have a person at our company who takes care of all PowerDB issues for us.

We use a mixture of forms and they need work. Our main DB is hosted elsewhere and we are constantly on the phone with support. How many techs do you have working in a DB?

[Kalbi_Rob]

All three of the companies I've worked for have used PowerDB. Each company had a different way of using PowerDB. My first company transferred over from Excel and Word documents to PowerDB. They also made the transition the best with a overall administrator who had a complaint/resolution intranet page dedicated to customizing powerDB pages. The second company printed off the sheets for techs, then hired a temp to input the data into powerDB (they didn't want to pay for multiple licenses). My current company has an administrator that doesn't understand PowerDB. Thus we are left with inadequate default test forms.
One unique way to sync, is to put a database on a thumb drive, sync your database with the master database, then with the thumb drive. You can then pass the thumb drive around a job site when internet access is limited, or you forget to create a job early. My first company did this and it worked great.

[SecondGen]

All three of the companies I've worked for have used PowerDB. Each company had a different way of using PowerDB. My first company transferred over from Excel and Word documents to PowerDB. They also made the transition the best with a overall administrator who had a complaint/resolution intranet page dedicated to customizing powerDB pages. The second company printed off the sheets for techs, then hired a temp to input the data into powerDB (they didn't want to pay for multiple licenses). My current company has an administrator that doesn't understand PowerDB. Thus we are left with inadequate default test forms.
One unique way to sync, is to put a database on a thumb drive, sync your database with the master database, then with the thumb drive. You can then pass the thumb drive around a job site when internet access is limited, or you forget to create a job early. My first company did this and it worked great.

Sounds like we may be in a similar situation, I think the biggest problem we have is lack of a dedicated DB person who has field experience. Our company used to do the memory stick method but now we sync to a central file on the cloud.

I constantly have issues trying to get my data to sync, attaching external documents is a nightmare in itself sometimes and how come they don't show up in the print dialog?! Our forms need work too, just little things like tab order and data field types would make a big difference.